Scope 0.3.0 acceptance to AWS clean installation - #13
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.
Version 0.3.0 now requires a real AWS/EKS clean installation and canonical trace acceptance through the Dashboard. Azure/AKS and GCP/GKE remain experimental; later releases retain the existing three-cloud, nine-check gate until that policy is separately reviewed.
The validator requires
installandcanonicalAcceptanceevidence for EKS. Optional experimental-cloud reports must satisfy the same checks and freshness rules, and a rollback declaration still requires recovery evidence. Exact source/image/requirements bindings, anonymous pulls, immutable artifact checks, and publication/catalog approval remain unchanged. No acceptance results are asserted or added by this PR.Updated the generated acceptance schema and operator documentation to describe this scope and the lifecycle behavior it does not certify.
Validation: 164 tests passed, 4 disposable-cluster tests skipped locally; focused publication tests (15) passed after independent review; Ruff lint/format, package builds, CRD admission validation, and Terraform formatting passed. CI still runs the full contract, Terraform, Kubernetes, and security matrix.