Repository navigation
deploy: enable internal qualified WasmEdge IRC canary - #3
Merged
Merged
Conversation
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.
Enable one loopback-only canary using the existing immutable OCI digest and verified dedicated RuntimeClass. Preserve all security boundaries, localhost bind, resources and configuration. No public ingress, privileges, RBAC changes or node restart. Recreate avoids overlapping canary revisions. Cloud Flux remains pinned to the previous suspended source until this exact head passes review/checks and a separate cloud pin/unsuspend change is qualified. Live server dry-run and kustomize render pass. HTTP recovered through cloud #7656 and passed 189 seconds actual Service/Ready endpoint stability; its historical restarts are not erased. Acceptance must prove two live clients registration/JOIN/NAMES/bidirectional PRIVMSG and restart recovery while HTTP remains stable. Pod Running alone is not IRC acceptance.