-
Notifications
You must be signed in to change notification settings - Fork 9.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
[bitnami/jaeger] migration job not using namespaceOverwrite #31216
[bitnami/jaeger] migration job not using namespaceOverwrite #31216
Conversation
1010315
to
712ba90
Compare
Hi @MarcoFuykschot , thanks for your contribution, could you please rebase from |
Signed-off-by: Marco Fuykschot <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
2f51b99
to
779d4e2
Compare
Done |
Signed-off-by: Bitnami Containers <[email protected]>
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.
Thanks for your contribution
Signed-off-by: Bitnami Containers <[email protected]>
Hi @MarcoFuykschot, Tests are returning 500 error messages when trying to connect to the test platform. Could you please update your branch with the latest changes in our repo? I'll take a look at the test results after that and merge the changes once they succeed. |
Hi @MarcoFuykschot, The issue may be related to the branch's name you used when pushing the changes. Apart from updating it, can you rename the branch removing the parenthesis (and recreate the PR if necessary)? I can see other jobs succeeded in our pipeline but this one continues failing. |
Pull request was closed
Date: Sa Jan 4 20:42 2028 +01:00
Description of the change
namespace of the migration-job is now using the include common.names.namespace
Benefits
namespaceOverride is consistent again
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.(https://github.com/bitnami/readme-generator-for-helm)