-
Notifications
You must be signed in to change notification settings - Fork 116
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-chart): resource namespace and name #462
fix(helm-chart): resource namespace and name #462
Conversation
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.
Nice! Could you update the field in the ClusterRoleBinding to match the new name(+space) of the ServiceAccount?
Sorry i forgot to change it there. |
Sorry for the delay. Our e2e tests are currently broken for PRs from forks and I wanted to run them locally. I found that in the e2e tests we do not set the Helm Chart namespace which caused the pods to run in |
🤖 I have created a release *beep* *boop* --- ## [1.17.0](v1.16.0...v1.17.0) (2023-07-18) ### Features * **helm:** allow to set labels and annotations for podMonitor ([#471](#471)) ([5dad655](5dad655)) * upgrade to hcloud-go v2 e4352ec ([5a066a1](5a066a1)) ### Bug Fixes * **helm-chart:** resource namespace and name ([#462](#462)) ([0c4eee6](0c4eee6)) * **routes:** deleting wrong routes when other server has same private IP ([#472](#472)) ([5461038](5461038)), closes [#470](#470) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This should fix the issue that you can change the release namespace with helm, but the deployment will not take care of it.
Also this allows the user to use the nameoverwrite that was already defined inside the chart helpers.