Add explicit-context cluster acceptance checks - #84
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
2 participants
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.
Add an explicit-context acceptance runner for an existing operator-managed Pulse installation. Default invocation contacts no cluster. Opt-in observations verify owned workload rollout state, pod image IDs, PostgreSQL policy and nginx stability. Separately selected checks exercise packet connectivity, token rotation/restoration and Temporal policy transitions in a disposable namespace.
Reports distinguish passed observations from incomplete overall release acceptance. Secret patches use stdin, probe cleanup uses UID preconditions, and checks fail on missing evidence or failed restoration. Document remaining deployed UI/API, RBAC and workflow persistence tests.
Validation: 16 mocked runner tests passed and are wired into CI. These validate runner behavior only; no real cluster or local Pulse stack was started.