From eed1a48fc0318e71947f86ef5ec4c1420064535c Mon Sep 17 00:00:00 2001 From: jklein Date: Sun, 23 Aug 2026 16:05:53 +0200 Subject: [PATCH] Update minecraft-server to the java17 line (0.4.0+upjava17) Second of the three Java-line publishes. Only the two version lines in Chart.yaml change; the rendered output differs from the published java8 chart in exactly one line, the image tag. The CI install values move along with the appVersion: the image tag is the Java line, so the JVM is fixed per published chart version and the Minecraft version has to match it (Java 8 runs up to 1.16.5, 1.18-1.20.4 need Java 17). No single Minecraft version boots on all three lines, and because the chart has no probes a version the JVM cannot load would still leave a green install-test behind. minecraft.version therefore moves 1.12.2 -> 1.20.1. ci/ is outside the chart directory and is neither packaged nor published. --- ci/minecraft-server/test-values.yaml | 14 +++++++------- minecraft-server/Chart.yaml | 4 ++-- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/ci/minecraft-server/test-values.yaml b/ci/minecraft-server/test-values.yaml index 7e9da95..533e560 100644 --- a/ci/minecraft-server/test-values.yaml +++ b/ci/minecraft-server/test-values.yaml @@ -3,13 +3,13 @@ # # 1. minecraft.version: the image tag comes from .Chart.AppVersion, so the JVM # in the image is fixed per published chart version and the Minecraft -# version has to match that Java line - Java 8 runs Minecraft up to 1.16.5, -# modern versions need Java 17/21 and refuse to start otherwise. This chart -# version publishes appVersion "java8", hence 1.12.2 (a classic Java 8 era -# release). This value is bumped together with appVersion in the java17 and -# java21 follow-up PRs. +# version has to match that Java line - Java 8 runs Minecraft only up to +# 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 -# a Java 8 JVM cannot load at all. +# needs Java 21 and would not start on this line. # 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 +25,7 @@ secrets: minecraftServerRef: vaults/CI/items/minecraft-server minecraft: - version: "1.12.2" + version: "1.20.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 51e8a53..49a513c 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+upjava8 +version: 0.4.0+upjava17 # 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: "java8" +appVersion: "java17"