Repository navigation
helm: use fullname template for FlowSchema priorityLevelConfiguration reference - #10979
Conversation
… reference The FlowSchema's spec.priorityLevelConfiguration.name was hardcoded as 'kueue-visibility' instead of using the Helm fullname template. When fullnameOverride or nameOverride is set, the FlowSchema references a non-existent PriorityLevelConfiguration, breaking the visibility API's APF configuration. Fix: - Update config source to use plain 'visibility' name (consistent with metadata.name pattern; kustomize nameReference handles the prefix) - Add APPEND operation in processing-plan.yaml for the PLC name field - Regenerate the Helm template to use the fullname template ```release-note Fixed FlowSchema priorityLevelConfiguration using hardcoded name instead of Helm fullname template, which broke APF when fullnameOverride or nameOverride was set. ```
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @cixuuz. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. 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. |
|
/ok-to-test |
|
Thank you 👍 |
|
@mimowo: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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-sigs/prow repository. |
|
LGTM label has been added. DetailsGit tree hash: d16e8fe7bf5221a5719147b2deef4b5ebd51c216 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cixuuz, mimowo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@mimowo: new pull request created: #10981 DetailsIn response to this:
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-sigs/prow repository. |
|
@mimowo: new pull request created: #10983 DetailsIn response to this:
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-sigs/prow repository. |
… reference (kubernetes-sigs#10979) The FlowSchema's spec.priorityLevelConfiguration.name was hardcoded as 'kueue-visibility' instead of using the Helm fullname template. When fullnameOverride or nameOverride is set, the FlowSchema references a non-existent PriorityLevelConfiguration, breaking the visibility API's APF configuration. Fix: - Update config source to use plain 'visibility' name (consistent with metadata.name pattern; kustomize nameReference handles the prefix) - Add APPEND operation in processing-plan.yaml for the PLC name field - Regenerate the Helm template to use the fullname template ```release-note Fixed FlowSchema priorityLevelConfiguration using hardcoded name instead of Helm fullname template, which broke APF when fullnameOverride or nameOverride was set. ```
|
/release-note-edit |
… reference (kubernetes-sigs#10979) The FlowSchema's spec.priorityLevelConfiguration.name was hardcoded as 'kueue-visibility' instead of using the Helm fullname template. When fullnameOverride or nameOverride is set, the FlowSchema references a non-existent PriorityLevelConfiguration, breaking the visibility API's APF configuration. Fix: - Update config source to use plain 'visibility' name (consistent with metadata.name pattern; kustomize nameReference handles the prefix) - Add APPEND operation in processing-plan.yaml for the PLC name field - Regenerate the Helm template to use the fullname template ```release-note Fixed FlowSchema priorityLevelConfiguration using hardcoded name instead of Helm fullname template, which broke APF when fullnameOverride or nameOverride was set. ```
What type of PR is this?
/kind bug
What this PR does / why we need it:
The FlowSchema's
spec.priorityLevelConfiguration.namewas hardcoded askueue-visibilityinstead of using the Helm fullname template. WhenfullnameOverrideornameOverrideis set in Helm values, the FlowSchema references a non-existent PriorityLevelConfiguration, breaking the visibility API's API Priority and Fairness configuration.Which issue(s) this PR fixes:
Fixes #10934
Changes:
config/components/visibility-apf/flowschema.yaml: ChangedpriorityLevelConfiguration.namefromkueue-visibilitytovisibility(consistent with howmetadata.nameis handled — kustomize nameReference propagates the prefix automatically)hack/processing-plan.yaml: Added an APPEND operation for.spec.priorityLevelConfiguration.nameso the yaml-processor generates the correct Helm templatecharts/kueue/templates/visibility-apf/flowschema.yaml: Updated the generated template to use{{ include "kueue.fullname" . }}-visibilityinstead of the hardcoded value