🐛 let the public health report complete in the k3d smoke - #680
Merged
Conversation
The health completeness gate added by #673 has never passed in CI, so develop has been red since it merged (its own validation run failed after the merge). Two defects: The channel-proxy ingress policy admitted only the ingress-controller namespace, so the server's new channel readiness probe was rejected (k3s answers with a reset, which surfaced as ECONNREFUSED against the service IP). The server-side egress rule now has its ingress counterpart. The smoke deployed no model, and LiteLLM answers /model/info with 500 on an empty estate, so the models probe could never turn available. The smoke now seeds the initial provider with a placeholder key: registration writes LiteLLM's model row without calling the provider. The channel-proxy chart stamps to 0.9.2 with its noop migration, and the umbrella pin, lock, and archive move with it.
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.
Why
Develop's k3d smoke has failed on every run since #673 merged (at 09:48, 18 minutes before its own validation run finished failing — first failing run). Every develop push and every PR since fails with the same signature:
Because develop is red, the smoke's PR skip-proof never fires either, so every open PR pays the full k3d run — this one failure is currently the single largest CI tax in the repository.
Root causes
ECONNREFUSEDagainst the service ClusterIP even though the pod is Ready). Fix: the matching ingress rule for the opencrane-server pods.GET /model/infowith 500 on an empty estate, so the models probe can never turn available. Fix: the smoke seeds--initial-model-provider openaiwith a placeholder key — registration only writes LiteLLM's model row and the probe lists the estate; neither path calls the provider.Versioning
The channel-proxy chart changed, so it stamps to 0.9.2 with a noop
0.8.0-to-0.9.2migration; the umbrella pin,Chart.lock, and packaged archive move with it.Validation
check:release-versioning --base origin/developPASS; affected-deployables tests 15/15Unblocks #677 and every other open PR.