Pin the agent-platform operator to 0.6.7 - #206
Merged
Merged
Conversation
0.6.5 is the operator built before two fixes to the code it runs. The first is the one that matters. Tenant egress was a static allow-list that never read spec.datastores, so a tenant declaring a relational store got Aurora provisioned, an IAM policy scoped to reach it, and a default-deny NetworkPolicy that dropped the packets. The Platform reports Ready, the datastore is available, the credential is valid, and the connection times out — nothing in the control plane disagrees with itself, so nothing reports a problem. Every tenant declaring a datastore has it, not one app. 0.6.7 derives the rules from the declaration: 5432, 6379 and 9098 for the kinds that speak their own protocol, and toFQDNs naming s3, dynamodb and sqs for the kinds that reach AWS on 443 — bounded by hostname because Bedrock answers on that same port from the same VPC, and a port-scoped rule there would give every application pod a direct route to the model plane. The second fix defaults a relational datastore to an Aurora major line rather than a patch AWS can retire. Chart 0.6.7 carries appVersion 0.6.1, so the image moves with it — the CRDs and the binary reconciling them advance together. 0.6.6 was never published; its contents moved before release, so the version was skipped rather than overwritten. The Application syncs automated with selfHeal, so this lands on the next poll without a manual sync.
CI Results
All checks passed. |
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
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.
0.6.5is the operator built before two fixes to the code it runs.The one that matters
Tenant egress was a static allow-list that never read
spec.datastores. So a tenant declaring a relational store got Aurora provisioned, an IAM policy scoped to reach it, and a default-deny NetworkPolicy that dropped the packets.Platform
Ready. Datastore available. Credential valid. Connection times out. Nothing in the control plane disagrees with itself, so nothing reports a problem.This affects every tenant that declares a datastore, not one app.
0.6.7derives the rules from the declaration:5432/6379/9098for relational, cache and stream — the kinds that speak their own protocoltoFQDNsnamings3/dynamodb/sqsfor objectStore, keyValue and queue — bounded by hostname, because Bedrock answers on that same 443 from the same VPC and a port-scoped rule would hand every application pod a direct route to the model planeVerified live from one tenant pod:
s3.us-west-2.amazonaws.com:443reachable,bedrock-runtime.us-west-2.amazonaws.com:443blocked.The second fix defaults a relational datastore to an Aurora major line rather than a patch AWS can retire.
Version chain
Chart
0.6.7carriesappVersion: 0.6.1, so the image moves with the chart — the CRDs and the binary reconciling them advance together, rather than a chart shipping fixes its operator doesn't have. The0.6.1image is published, multi-arch, signed and attested; chart0.6.7is confirmed present in the registry.0.6.6was never published — its contents moved before release, so the version was skipped rather than overwritten.Rollout
The Application syncs
automatedwithselfHeal, so this lands on the next poll without a manual sync. Local gates pass: chart-provenance (30 pins, all recorded), its self-test (5 breaks rejected), and catalog-revision (25 sources readinggitops/repo-branch).