fix(connectivity): the s3proxy façade declares ephemeral-storage requests and limit and bounds its emptyDirs (#438) - #440
Merged
Conversation
Published Helm chart
|
| Chart | agent-platform |
| Version | 4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18 |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform:4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18 |
| Digest | sha256:2c6a098bf0041e9e93fe802716f00bdc6a73e230e5decbc2b127359974933ee1 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform --version 4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18Posted by architect-orb · build 7382 · commit b2bfe18 · updated in place on every push
Published Helm chart
|
| Chart | agent-platform-connectivity |
| Version | 4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18 |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity:4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18 |
| Digest | sha256:2a07ac3841426dd60918f401a3a49d2bee41bc592b36b49c1a5eda727d9b8a05 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity --version 4.10.6-dev.fix-s3prox--ral-storage.2026-09-14.10-23-40.hb2bfe18Posted by architect-orb · build 7383 · commit b2bfe18 · updated in place on every push
…ests and limit and bounds its emptyDirs — Kyverno require-emptydir-requests-and-limits (#438) The substrate-s3proxy container mounts two emptyDirs (/tmp for the JVM, the image's /data) and carried no ephemeral-storage requests or limits, so Kyverno's require-emptydir-requests-and-limits (Audit on the fleet) reported the Deployment on every rollout (glean, connectivity 4.10.3 and 4.10.4). kagent.harness.snapshotStore.s3proxy.resources now defaults requests.ephemeral-storage 256Mi and limits.ephemeral-storage 1Gi in both charts (the meta chart forwards the block), both emptyDirs take the limit as their sizeLimit, and the render refuses a resources block without either field. verify-substrate-store asserts the fields, the bound, the knob, the forwarded default and the guard on the capz and the façade-alone shapes; verify-components holds the two charts' resources defaults together. UPGRADE.md: the façade's two pods roll once.
teemow
force-pushed
the
fix/s3proxy-ephemeral-storage
branch
from
September 14, 2026 10:24
9dcab8a to
b2bfe18
Compare
3 tasks
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.
Fixes #438.
Problem
The
substrate-s3proxycontainer (kagent.harness.snapshotStore.s3proxy, on with providercapzors3proxy.enabled) mounts two emptyDirs —/tmpfor the JVM and the image's/data— withoutephemeral-storagerequests or limits. Kyverno'srequire-emptydir-requests-and-limits(Audit on the fleet) reports it on every rollout:Seen on glean with connectivity 4.10.3 and 4.10.4 (2026-09-13) — the one Kyverno finding the platform leaves on a fresh 4.x installation; a cluster that enforces the policy would refuse the façade.
Change
kagent.harness.snapshotStore.s3proxy.resourcesdefaultsrequests.ephemeral-storage: 256Miandlimits.ephemeral-storage: 1Giin both charts (the meta chart forwards the block; the façade streams, nothing of a snapshot lands on its disk, so a small bound is enough).sizeLimit(--set …resources.limits.ephemeral-storage=2Gimoves both).…s3proxy.resources.<requests|limits>.ephemeral-storage is required).make verify-substrate-store: the fields, the bound (noemptyDir: {}left), the knob, the forwarded default in the meta chart's connectivity release, and the guard — on the capz and the façade-alone shapes.tests/verify-components.py: the two charts's3proxy.resourcesdefaults are one, with ephemeral-storage in requests and limits.Adjacent, kept: #437's
JCLOUDS_CREDENTIAL: ""on the capz branch; #435's re-pins.Verification
make verify-substrate-storeandmake verify-componentspass locally and inexecute-chart-tests.hack/agentlab/, meta chart installed from this branch's dev build4.10.5-dev.fix-s3prox--ral-storage.2026-09-14.09-43-01.h864b91f, the connectivity release pinned to the same tag):ephemeral-storagerequests/limits on the pods (the 4.10.4 template passesresourcesthrough); the emptyDirs stayed unbounded. A probeAgentTemplatewent Ready in ~15 s, its golden snapshot (5 objects, 1.3 MiB) landed in Azurite through the façade.platform-testall PASS.requests.ephemeral-storage: 256Mi,limits.ephemeral-storage: 1Gi, both emptyDirssizeLimit: 1Gi. A second probe template created right after went Ready in 5 s; its golden snapshot (probe-438-b-kagent-1e299b5e8488, 5 objects) was written through the rolled façade at 10:19:55Z.platform-testall PASS again.PolicyViolationevent onsubstrate-s3proxy(baseline before: onerequire-emptydir-requests-and-limitsevent, the Deployment withoutephemeral-storage).