Files
helm-charts/minecraft-server/Chart.yaml
T
jklein 4a7ee1036c feat(minecraft-server): networkPolicy.ingress.ambientMesh
Gitea #143. Additive, default false, so the render is byte-identical to the
previous release - proven by diffing both renders against origin/main rather
than asserted.

Switched on it adds 15008/TCP, ztunnel's HBONE tunnel, to the rule carrying
the probe port, and - inside that rule's source-restricted branch -
169.254.7.127/32, the address the kubelet's probes arrive from once the pod is
in the mesh. Ambient does not bypass NetworkPolicy enforcement, so without the
port a pod whose namespace has joined the mesh is unreachable.

The two halves are one value because the second is the one nobody thinks of:
15008 added by hand leaves a policy that passes review and drops every probe
the first time probeSources is narrowed, and a pod that never becomes Ready
reads as a broken application rather than as a policy.

Minor, not major: additive value, unchanged default, unchanged render.

Port half only: this chart offers no networkPolicy.probeSources - its probes
put no packet on the network - so there is no redirected probe to allow and an
ipBlock for one would match nothing while making the rule look like it did
something. ci/run-networkpolicy-test.sh ties that exemption to the absence of
probeSources, not to a chart name.
2026-10-19 17:56:58 +00:00

31 lines
1.5 KiB
YAML

apiVersion: v2
name: minecraft-server
description: A Helm chart for deploying a itzg/minecraft-server
icon: https://avatars.githubusercontent.com/u/988985
type: application
# ONLY THE NEWEST JAVA LINE IS MAINTAINED (chart 5.0.0, issue #158).
# appVersion is the image tag and therefore fixes the JVM. Up to chart 4.1.0 the
# chart was published once per line (java8 / java17 / java21 / java25) out of
# this single directory, which is what made the lines drift apart: whatever
# change landed while a line happened to lie in the directory reached that line
# only. That is over. This directory carries exactly one line - the newest -
# and it is the only one that gets chart changes.
# The older lines stay published as frozen artifacts and are still installable:
# java8 and java17 at 4.0.0, java21 at 4.1.0. They will not be updated again.
# To run an older JVM with the CURRENT chart, set image.tagOverride in values
# instead of installing a frozen chart version; the chart then checks that
# minecraft.version fits the line of that tag and fails the render if it does
# not.
# Since chart 2.0.0 the tag is a DATED upstream release ("<release>-java<N>")
# instead of the rolling line tag ("java<N>"): the rolling tags are rebuilt
# continuously, so a pod restart could pull a different image than the last one
# without anything being recorded anywhere. The dated tags are immutable, so the
# image is now pinned by the chart version like every other chart in this repo.
version: 7.1.0+up2026.8.2.java25
appVersion: "2026.8.2-java25"
maintainers:
- name: jklein