Merge pull request #85 from jk-cluster/feat/minecraft-router-config-checksum

Restart the router when its routing config changes (minecraft-router 2.0.0+up1.46.4)

minecraft-router/Chart.yaml

@@ -5,7 +5,7 @@ icon: https://avatars.githubusercontent.com/u/988985
 
 type: application
 
-version: 1.0.1+up1.46.4
+version: 2.0.0+up1.46.4
 appVersion: "1.46.4"
 
 maintainers:

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

@@ -14,6 +14,13 @@ spec:
       name: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
       labels:
         app: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+      annotations:
+        # Rolls the pod whenever the rendered routing ConfigMap changes.
+        # Without it a changed routing table stays inert: the file is mounted
+        # with subPath (kubelet never refreshes those in a running container)
+        # and mc-router reads ROUTES_CONFIG only at startup, so the router
+        # would keep serving the old routes while everything looks healthy.
+        checksum/config: {{ include (print $.Template.BasePath "/minecraft-router.configmap.yaml") . | sha256sum }}
     spec:
       automountServiceAccountToken: false
       securityContext:

minecraft-router/values.yaml

@@ -15,6 +15,11 @@ scaleDown: false
 #     - domain: creative.example.com
 #       internalUrl: creative-service.minecraft.svc.cluster.local
 #       port: 25566
+# Since chart 2.0.0 a change here rolls the router pod: the deployment carries
+# a checksum/config annotation over the rendered ConfigMap. That restart is
+# required for the change to take effect at all - the config is mounted with
+# subPath and mc-router only reads it at startup - and costs a few seconds of
+# proxy downtime, during which clients cannot connect.
 mappings: null
 
 server: