Skip to content

Pin the agent-platform operator to 0.6.7 - #206

Merged
stxkxs merged 1 commit into
mainfrom
pin-operator-0.6.7
Aug 11, 2026
Merged

Pin the agent-platform operator to 0.6.7#206
stxkxs merged 1 commit into
mainfrom
pin-operator-0.6.7

Conversation

@stxkxs

@stxkxs stxkxs commented Aug 11, 2026

Copy link
Copy Markdown
Member

0.6.5 is 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.7 derives the rules from the declaration:

  • 5432 / 6379 / 9098 for relational, cache and stream — the kinds that speak their own protocol
  • toFQDNs naming s3 / dynamodb / sqs for 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 plane

Verified live from one tenant pod: s3.us-west-2.amazonaws.com:443 reachable, bedrock-runtime.us-west-2.amazonaws.com:443 blocked.

The second fix defaults a relational datastore to an Aurora major line rather than a patch AWS can retire.

Version chain

Chart 0.6.7 carries appVersion: 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. The 0.6.1 image is published, multi-arch, signed and attested; chart 0.6.7 is confirmed present in the registry.

0.6.6 was never published — its contents moved before release, so the version was skipped rather than overwritten.

Rollout

The Application syncs automated with selfHeal, 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 reading gitops/repo-branch).

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.
@github-actions

Copy link
Copy Markdown

CI Results

Check Status
Zero-placeholder gate ✅ success
YAML Lint ✅ success
Dashboard gate (live grafana.com ids + AMG-saveable) ✅ success
Kyverno policy tests (+ verify-images contract) ✅ success
Fork-safety gate (no hardcoded org, blocking) ✅ success
Helm-render (every addon × every env) ✅ success
Policy-admission (Enforce-tier Kyverno vs the fleet) ✅ success
ApplicationSet schema + sync waves ✅ success
Appset render (Karpenter subnet selector) ✅ success
Secret scan (gitleaks) ✅ success
Render + assert + schema + misconfig (all environments) ✅ success

All checks passed.

@stxkxs
stxkxs merged commit a59ce04 into main Aug 11, 2026
23 checks passed
@stxkxs
stxkxs deleted the pin-operator-0.6.7 branch August 11, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant