K8s Helm chart baseline (#5)

chart/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

chart/Chart.lock

@@ -0,0 +1,12 @@
+dependencies:
+- name: nats
+  repository: https://nats-io.github.io/k8s/helm/charts/
+  version: 1.1.5
+- name: redis
+  repository: https://charts.bitnami.com/bitnami
+  version: 18.4.0
+- name: mysql
+  repository: https://charts.bitnami.com/bitnami
+  version: 9.14.3
+digest: sha256:808e95ad8dcfb99e1b75fd06f50b9695e350eb768bc08eb957ab5f72a58bd4e7
+generated: "2023-11-16T21:07:35.87621062+01:00"

chart/Chart.yaml

@@ -0,0 +1,38 @@
+apiVersion: v2
+name: tocloud9
+description: A Helm chart for Kubernetes
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 0.1.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: "1.16.0"
+
+dependencies:
+- name: nats
+  version: "1.1.5"
+  condition: nats.enabled
+  repository: "https://nats-io.github.io/k8s/helm/charts/"
+- name: redis
+  version: "18.4.0"
+  condition: redis.enabled
+  repository: "https://charts.bitnami.com/bitnami"
+- name: mysql
+  version: "9.14.3"
+  condition: mysql.enabled
+  repository: "https://charts.bitnami.com/bitnami"

chart/README.MD

@@ -0,0 +1,24 @@
+# ToCloud9 Helm chart
+
+This chart will deploy a ToCloud9 cluster using **AzerothCore** as backend.
+
+> **WARNING:_** 
+Pre-built images in this chart values won't be actively maintained, build your own ones if you want to be up to date with AzerothCore releases.
+
+## How to use
+
+1. Check the values to set a storage class for persistency and load-balancer domain.
+2. Deploy the chart
+3. Most services won't start as long as the databases tables aren't initialized with the [AzerothCore sql scripts](https://github.com/azerothcore/azerothcore-wotlk/tree/master/data/sql/base) and [ToCloud9 modifications](../doc/RunNonDockerWinWSLAzerothCore.md#setup--run). Databases and user are already created during mysql deployment.
+4. Gameserver will require its `/data` volume to be provisionned with files to be [downloaded](https://www.azerothcore.org/wiki/server-setup#download) or [extracted](https://www.azerothcore.org/wiki/server-setup#extractors).
+5. If you don't localhost as "domain" and port forwarding to both auth server and lb, you need to update the auth database realmlist table with propre informations, ie :
+```sql
+UPDATE realmlist
+SET
+  name = 'myawesomerealmname',
+  address = 'wow.myawesome.domain',
+  localAddress = '192.168.1.X',
+  localSubnetMask = '255.255.255.0',
+  port = 8085
+WHERE id=1;
+```