fix: export KUBECONFIG inline and poll until k3s API is ready - #10
Merged
Conversation
Two bugs in the Start k3s step: 1. KUBECONFIG was set only via $GITHUB_ENV, which applies to subsequent steps but not the current run: block — kubectl was hitting localhost:8080 (empty). Fix: also export KUBECONFIG in the same shell. 2. kubectl wait ran immediately after systemd started k3s, before the API server was up. Fix: poll with until kubectl get nodes until it responds. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Root cause
Two bugs in the
Start k3sstep causedkubectl waitto fail with connection refused on localhost:8080:Bug 1 — KUBECONFIG not visible within the same step
$GITHUB_ENVwrites are picked up at the start of the next step, not within the currentrun:block. Fix: alsoexport KUBECONFIG=...in the same shell.Bug 2 — kubectl ran before the API server was up
k3s installs as a systemd service and starts asynchronously.
kubectl waitwas called less than 1 second aftersystemd: Starting k3s, before the API server was listening. Fix: poll withuntil kubectl get nodes &>/dev/null; do sleep 3; done.🤖 Generated with Claude Code