-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(helm): only default bucket names when using minio #12548
Conversation
13c031d
to
3667d2a
Compare
bucketNames: | ||
chunks: chunks | ||
ruler: ruler | ||
admin: admin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of deleting this, maybe comment it out with FIXME for the names?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@trevorwhitney upgrading from 6.0 to 6.1 and the error below happens. There is a high chance this PR breaks current installations where the defaults for storage are not defined
|
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-12548-to-helm-5.47.3 origin/helm-5.47.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 2e32ec52d8766c0a5a75be30585402f1dce52cc5 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-12548-to-helm-5.47.3
# Create the PR body template
PR_BODY=$(gh pr view 12548 --json body --template 'Backport 2e32ec52d8766c0a5a75be30585402f1dce52cc5 from #12548{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "chore: [helm-5.47.3] fix(helm): only default bucket names when using minio" --body-file - --label "size/M" --label "area/helm" --label "type/docs" --label "type/bug" --label "product-approved" --label "backport" --base helm-5.47.3 --milestone helm-5.47.3 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-12548-to-helm-5.47.3
# Create a pull request where the `base` branch is `helm-5.47.3` and the `compare`/`head` branch is `backport-12548-to-helm-5.47.3`.
# Remove the local backport branch
git switch main
git branch -D backport-12548-to-helm-5.47.3 |
(cherry picked from commit 2e32ec5)
@luong-komorebi would you mind sharing a bit of information about your install? I think the goal here is to intentionally break any installation using the default buckets with a cloud provider as you likely don't own those buckets and don't mean to send data there? Was your installation using the defaults, and if so, were you only using it to query recent data? |
Commenting out Helm lint create errors of type I would propose adding a default value, something like
What do you think? I can open an MR if you think that makes sense. Thank you! |
@trevorwhitney sorry Trevor, I was late to this due to being busy. Yes my installation was pretty much default. However, I did have storage config inside which I define an s3 bucket name # something like this
storage_config:
aws:
bucketnames: abc-prod-logs
region: us-west-2
s3forcepathstyle: true and I dont configure other things like this breaks after I upgraded Later I do have to configure other things so the app can work again ( cant recall what I configured, but it seems like I needed to add : storage = {
type = "s3"
bucketNames = {
chunks = "chunks"
ruler = "ruler"
admin = "admin"
}
}
# and
minio = { enabled = false } ) because these are what caused the app to break. I think there are some defaults that the upgrade fails to handle or notice maintainers |
@Farfaday Do you plan to open a PR? :) |
What this PR does / why we need it:
Only default bucket names in helm when using minio.