Repository navigation
[Backport release-1.7] feat(bucket): add a ui flag to skip the s3manager web UI - #5147
Open
mattia-eleuteri wants to merge 1 commit into
Open
mattia-eleuteri wants to merge 1 commit into
mattia-eleuteri wants to merge 1 commit into
Conversation
Every bucket ships an s3manager Deployment with its Service and an Ingress or HTTPRoute on <bucket>.<tenant host>. Tenants that only use the S3 API pay for a pod per bucket and for one DNS name and TLS certificate per bucket, none of which they need. ui defaults to true, so existing buckets keep their UI. With ui set to false the bucket no longer needs the tenant apex either, since the UI hostname was its only consumer in the bucket-system chart. Assisted-by: LLM Signed-off-by: Mattia Eleuteri <[email protected]> (cherry picked from commit 0c62bee) Signed-off-by: Mattia Eleuteri <[email protected]>
mattia-eleuteri
added
the
kind/backport
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
github-actions
Bot
added
size/L
mattia-eleuteri
marked this pull request as ready for review
October 28, 2026 13:09
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.
What this PR does
Backport of #4881 to release-1.7, alongside #5146 for release-1.6.
The
bucket-<name>-systemrelease renders the users' credentials Secrets as well as the s3manager UI, and its install waits for the s3manager pod. When the tenant quota refuses that pod, the install times out and no user of the bucket gets credentials for 10 minutes or more. Operators who do not use the UI need the flag on 1.7 to take the pod out of that path.0c62bee4d, the only commit of #4881, applies cleanly: release-1.7 already hascozy-lib.ns-host-requiredand the_cluster: {}default in the bucket-system values, so unlike #5146 neither a conflict resolution nor a test adaptation is needed.make -C packages/apps/bucket generateleaves no diff, twice in a row.helm unittest packages/apps/bucket: 11 passed.helm unittest packages/system/bucket: 17 passed.helm templateofpackages/system/bucketrenders the Service, Deployment and Ingress (or HTTPRoute behind a Gateway) withui: true, none of them withui: false, and withui: falserenders without a tenant apex;packages/apps/bucketpassesuithrough to the HelmRelease values in both cases.Screenshots
Not a UI change: the flag removes the s3manager UI, it does not change it.
Downstream repositories
Walked the trigger map against the diff. As in #4881, a new field in
packages/apps/bucket/values.schema.jsonreaches the Terraform provider and the hand-written Bucket page of the website; both follow-ups already exist as issues. The website issue targetscontent/en/docs/next/; whether the v1.6 docs get the same section is left to the docs maintainers.Release note