From 198058b8bb6adda906e790f9c5527420b4683981 Mon Sep 17 00:00:00 2001 From: jklein Date: Sun, 23 Aug 2026 16:12:15 +0200 Subject: [PATCH] Update minecraft-server to the java21 line (0.4.0+upjava21) Last of the three Java-line publishes; main comes to rest on java21, the line of the only running server, and the registry holds all three tags. Only the two version lines in Chart.yaml change. Because the source chart in cluster-config is itself on java21, this final state renders byte-identical to it for mc-ftb-skies-2 with its real values file - the published end state is exactly what cluster-config runs today. The CI install values move along with the appVersion, as in the java17 PR: the JVM is fixed per published chart version and no single Minecraft version boots on all three lines. Since the chart has no probes, a version the JVM cannot load would crash after the rollout returned and still leave a green install-test behind. minecraft.version therefore moves 1.20.1 -> 1.21.1, which is also what ftb-skies-2 sets in its real values file, so CI exercises the production version. ci/ is outside the chart directory and is neither packaged nor published. --- ci/minecraft-server/test-values.yaml | 10 ++++++---- minecraft-server/Chart.yaml | 4 ++-- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/ci/minecraft-server/test-values.yaml b/ci/minecraft-server/test-values.yaml index 533e560..bb15dd7 100644 --- a/ci/minecraft-server/test-values.yaml +++ b/ci/minecraft-server/test-values.yaml @@ -7,9 +7,11 @@ # 1.16.5, 1.18-1.20.4 need Java 17, and 1.20.5+ need Java 21. No single # Minecraft version boots on all three lines, so this value is bumped # together with appVersion in every Java-line PR. -# This chart version publishes appVersion "java17", hence 1.20.1. -# The production default is "LATEST", which would pull a 1.21.x server that -# needs Java 21 and would not start on this line. +# This chart version publishes appVersion "java21", hence 1.21.1 - which is +# also what ftb-skies-2, the one server actually running on this line, sets +# in its real values file, so CI exercises the production version rather +# than an arbitrary Java-21-capable one. +# The production default is "LATEST", which would drift on every restart. # 2. minecraft.resources.storage: the production 32Gi world volume is backed by # a static hostPath PV in CI (see fixtures.yaml); 2Gi is plenty for a server # that only has to boot. @@ -25,7 +27,7 @@ secrets: minecraftServerRef: vaults/CI/items/minecraft-server minecraft: - version: "1.20.1" + version: "1.21.1" management: # opPlayers deliberately stays at the default (null): the image resolves # every name in OPS against the external Playerdb API and aborts the whole diff --git a/minecraft-server/Chart.yaml b/minecraft-server/Chart.yaml index 49a513c..9a8d9af 100644 --- a/minecraft-server/Chart.yaml +++ b/minecraft-server/Chart.yaml @@ -15,10 +15,10 @@ 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.4.0+upjava17 +version: 0.4.0+upjava21 # 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: "java17" +appVersion: "java21"