Import minecraft-router chart unchanged (Fleet migration stage 1)

Takes the existing mc-router chart over from cluster-config as-is so the
deployment can move to Fleet without any change to the rolled-out state.
Convention alignment follows in stage 2, the app update in stage 3.

The only deviation from "unchanged": Chart.yaml carried name:
minecraft-server (copy-paste from the sister chart). The publish job pushes
by the glob <directory>-*.tgz while helm package names the archive after the
Chart.yaml name, so without this correction the push finds no file.

Version 0.1.1+up1.25.1 - chart semver stays at 0.1.1, the +up suffix is repo
policy and does not affect rendering.

Also wires up CI: publish workflow, change-app-version choice list,
install-test values (CI-only node-port override, since 25565 is outside the
k3d default range) and the README chart table.

minecraft-router/.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/

minecraft-router/Chart.yaml

@@ -0,0 +1,24 @@
+apiVersion: v2
+name: minecraft-router
+description: A Helm chart for deploying a itzg/mc-router
+
+# 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.1+up1.25.1
+
+# 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.25.1"

minecraft-router/templates/mc-router-config.yaml

@@ -0,0 +1,15 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: {{ .Release.Name }}-config
+data:
+  custom-routing-config.json: |
+    {
+      "mappings": {
+    {{- $length := len .Values.mappings }}
+    {{- $indexLength := sub $length 1 }}
+    {{- range $index, $value := .Values.mappings }}
+        "{{ $value.domain }}": "{{ $value.internalUrl }}:25565"{{ if lt $index $indexLength }},{{ end }}
+    {{- end }}
+      }
+    }

minecraft-router/templates/mc-router-deployment.yaml

@@ -0,0 +1,48 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: {{ .Release.Name }}-deployment
+  labels:
+    app: {{ .Release.Name }}
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: {{ .Release.Name }}-deployment
+  template:
+    metadata:
+      name: {{ .Release.Name }}-deployment
+      labels:
+        app: {{ .Release.Name }}-deployment
+    spec:
+      automountServiceAccountToken: false
+      containers:
+        - image: "itzg/mc-router:{{ .Chart.AppVersion }}"
+          name: mc-router
+          args: ["--api-binding", ":8080"]
+          ports:
+            - name: proxy-port
+              containerPort: 25565
+            - name: api-port
+              containerPort: 8080
+          env:
+            - name: ROUTES_CONFIG
+              value: /data/custom-routing-config.json
+          resources:
+            requests:
+              memory: 50Mi
+              cpu: "100m"
+              ephemeral-storage: "50Mi"
+            limits:
+              memory: 100Mi
+              cpu: "250m"
+              ephemeral-storage: "500Mi"
+          volumeMounts:
+            - name: config-mount
+              mountPath: /data/custom-routing-config.json
+              subPath: custom-routing-config.json
+
+      volumes:
+        - name: config-mount
+          configMap:
+            name: {{ .Release.Name }}-config

minecraft-router/templates/mc-router-service.yaml

@@ -0,0 +1,14 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: {{ .Release.Name }}-service
+spec:
+  selector:
+    app: {{ .Release.Name }}-deployment
+  ports:
+    - nodePort: {{ .Values.server.outwardPort }}
+      port: 25565
+      targetPort: 25565
+      name: proxy-port
+  type: NodePort
+  

minecraft-router/values.yaml

@@ -0,0 +1,9 @@
+server:
+  # nodePort of the router Service. 25565 is the Minecraft default port and is
+  # deliberately outside the Kubernetes default node-port range (30000-32767) -
+  # the cluster runs an extended --service-node-port-range. Do NOT "fix" this
+  # into the default range: the Minecraft clients connect to this exact port.
+  outwardPort: 25565
+mappings:
+  - domain: null
+    internalUrl: null