-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
helm: Add Support for Namespace Override #24445
Conversation
Thanks for your help. There is small failure with generated doc checking, can you run the below command and submit the changes in the same commit ? https://github.com/cilium/cilium/actions/runs/4455626054/jobs/7829681639?pr=24445
|
/test |
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.
Looks good to me, thank you!
I can't help but feel like this needs a CI test so we can actually verify this works as expected. Do we have a good way for a contributor to add new GitHub workflows? |
Hmm, what's the use-case for this? Out of curiosity, why is the Helm namespace not sufficient? I see mention of umbrella charts, but can you explain that a bit more? Separately, are there other Helm conventions we should be implementing as well? |
Personally I wanted to deploy cilium via argo-cd with custom values, using sync waves so that cilium is installed first. |
This is helpful while deploying charts using gitOps tools like argoCD. Usually a standard among all the charts. - Patch for the helper.tpl priority class issue - document generation steps - spellcheck allowlist - make install/kubernetes Fixes: cilium#20511 Signed-off-by: Prateek Mishra <pr0PM@pm.me>
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment Job 'Cilium-PR-K8s-1.16-kernel-4.19' hit: #22578 (96.99% similarity) |
Hi just following up, I hope nothing else is pending from my side. |
I've kicked off some of the failed jobs; likely a flake but it's possible something somehow broke in the charts. |
@pr0PM looks like this needs a rebase; then it should be good to go. |
Signed-off-by: Prateek Mishra <pr0PM@pm.me>
hi can you provide steps on the kind of state we need here, i tried rebase but it didn't help in this case due to normal out of date from main and the switch from master -> main ig. |
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 the patch @pr0PM! This PR needs to be rebased on top of main
. A couple of files were removed and there is one conflict. Also git grep Release.Namespace
shows some instances of .Release.Namespace
that could be updated.
@@ -4,6 +4,9 @@ | |||
# For example: 1.7, 1.8, 1.9 | |||
# upgradeCompatibility: '1.8' | |||
|
|||
# -- String to override release namespace for all resources |
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.
Can we add a bit more of context here? e.g. mention that it is useful for tools that are unable to pass other Helm flags than values like argo-cd.
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 @pr0PM! Are you going to replace more .Release.Namespace
in install/kubernetes/cilium
?
Uh oh. It looks like you created a rebase commit instead of rebasing. You might just want to create a new branch off of main and cherry-pick your commit on top of it. |
I've marked the PR as draft while you address the feedback on the PR, feel free to click the "Ready for review" button at the bottom of the page to re-request review when you've addressed that. Thanks for your contributions! |
This pull request has been automatically marked as stale because it |
This pull request has not seen any activity since it was marked stale. |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
This is helpful while deploying charts using gitOps tools like argoCD. Usually a standard among all the charts.
Fixes: #20511
Signed-off-by: Prateek Mishra pr0PM@pm.me