Repository navigation
Conversation
Helm 4 server-side apply claims .rules when the chart sets rules: []. clusterrole-aggregation-controller already owns that field, so the next upgrade conflicts. Leave rules unset and let the aggregator fill them in. Signed-off-by: Dean Chen <862469039@qq.com>
|
Hi @locker95. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
closing this. #3127 landed the same chart change (drop rules: [] on the aggregated manila ClusterRoles). |
What this PR does / why we need it:
Helm 4 applies with server-side apply. The manila chart's aggregated controller/node ClusterRoles set
rules: [], so Helm takes ownership of.rules. After install,clusterrole-aggregation-controllerfills that field, and the nexthelm upgradedies with a conflict on.rules.Drop
rulesfrom those two templates. The aggregator still writes the real rules; Helm just stops claiming the field.Which issue this PR fixes:
fixes #3119
Special notes for reviewers:
helm lintis clean.helm templateno longer emitsruleson the aggregated ClusterRoles. Static manifests are unchanged.Release note: