-
Notifications
You must be signed in to change notification settings - Fork 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
Helm Chart bug, can not use a cascading expander with priority in it #4503
Helm Chart bug, can not use a cascading expander with priority in it #4503
Conversation
Welcome @AndrewFarley! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AndrewFarley The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Related to: #4321 With both of these fixed, proper support for expander priority will be fully capable in the helm chart |
I'm fully CLA'd, please @ me if you need anything else. Please fix, accept, and publish new Helm Charts ASAP if possible. Thanks |
…c in role.yaml template
Found a bug, fixed role.yaml which also used the old eq logic. Fixed to use contains logic, now the output is exactly the same. |
Hi @AndrewFarley, thanks for the PR! The chart version will need a bump here before we can merge it. /assign @gjtempleton |
Note: Safe to merge now, but this feature won't work until #4504 is resolved. |
@AndrewFarley: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
FYI, it looks like someone else fixed this in another MR/PR in e4cf3b0 but I think perhaps theirs was incomplete and missing some stanzas I included to handle all edge cases. Can someone/whomever merged that verify the merged code against my code in this MR to ensure it handled all edge cases? |
Sorry, my bad in terms of reviewing order. I assume from the merging of #4665 and your update to the comment there, we can close this PR now? |
Yep, closed |
Fixes #4502