Repository navigation
fix(ark): add a startup probe — liveness was killing the 13GB first install - #15
Merged
Merged
Conversation
…nstall ARK's first boot downloads ~13 GB of game via SteamCMD (plus Proton). The liveness probe fired 5 minutes in (initialDelay 180s + 5x30s), killed the container mid-download, and the server crash-looped forever — it could never reach a state where RCON listens, so liveness could never pass. Observed on the test cluster. A startup probe suspends liveness and readiness until it first succeeds, so the install now gets up to an hour; the normal liveness window only takes over once the server is actually up. This is the standard Kubernetes answer to a slow-starting container, and initialDelaySeconds on liveness/readiness is now redundant, so it's dropped. Signed-off-by: valgulnecron <39313199+ValgulNecron@users.noreply.github.com>
This was referenced Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ARK's first boot downloads ~13 GB of game via SteamCMD (plus Proton). The liveness probe fired 5 minutes in (
initialDelay 180s + 5 × 30s), killed the container mid-download, and the server crash-looped forever — it could never reach a state where RCON listens, so liveness could never pass. Observed on the test cluster.A startup probe suspends liveness and readiness until it first succeeds, so the install now gets up to an hour; the normal liveness window only takes over once the server is actually up. That's the standard Kubernetes answer to a slow-starting container.
initialDelaySecondson liveness/readiness is now redundant and dropped.Worth noting for other SteamCMD games: any template whose first boot pulls multi-GB content needs a startup probe, or its liveness window silently becomes a hard deadline on the download.