Remove invalid kustomizeconfig from config/webhook #5982
Merged
+0
−29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change has no effect on the output of this kustomization, but fixes a bug which can be triggered when using it as a base for another kustomization. kustomizeconfig contained 3 directives: * nameReference * namespace * varReference varReference is redundant because vars are no longer used in this kustomize: they are deprecated and usage was removed some time ago. nameReference is redundant because the specified configuration is already in kustomize's defaults. However, nameReference is the only important transformation here. namespace is incorrect. It directs the namespace transformer to update webhooks/clientConfig/service/namespace. However, this is not the intended function of the namespace transformer: it should only set the namespace directly on objects and allow references to be updated automatically by nameReference. Configuring it to update a reference directly leaves kustomize with inconsistent internal state. Depending on execution order this can cause a subsequent transformation to fail to update the reference when it makes further changes to the Service object.
k8s-ci-robot
added
the
release-note-none
k8s-ci-robot
added
size/S
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5982 +/- ##
=======================================
Coverage 44.53% 44.54%
=======================================
Files 279 279
Lines 25140 25140
=======================================
+ Hits 11197 11199 +2
+ Misses 13130 13128 -2
Partials 813 813 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was referenced Nov 21, 2025
Merged
Merged
Contributor
Author
|
/test pull-cluster-api-provider-azure-ci-entrypoint |
Contributor
Author
|
Doesn't look related. Hopefully a flake. /test pull-cluster-api-provider-azure-e2e |
mboersma
approved these changes
Nov 24, 2025
Contributor
mboersma
left a comment
mboersma
left a comment
There was a problem hiding this comment.
/lgtm
/approve
Thank you for cleaning this up!
k8s-ci-robot
added
the
lgtm
Contributor
|
LGTM label has been added. Git tree hash: 2142615c9a1e1994a24176252193c12850f9a73d
|
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mboersma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
This change has no effect on the output of this kustomization because the removed configuration was redundant. However, it fixes a bug which can be triggered when using this kustomization as a base for another kustomization.
kustomizeconfig contained 3 directives:
varReference is redundant because vars are no longer used in this
kustomize: they are deprecated and usage was removed some time ago.
nameReference is redundant because the specified configuration is
already in kustomize's defaults. However, nameReference is the only
important transformation here.
namespace is incorrect. It directs the namespace transformer to update
webhooks/clientConfig/service/namespace. However, this is not the
intended function of the namespace transformer: it should only set the
namespace directly on objects and allow references to be updated
automatically by nameReference. Configuring it to update a reference
directly leaves kustomize with inconsistent internal state. Depending on
execution order this can cause a subsequent transformation to fail to
update the reference when it makes further changes to the Service
object.
This issue is common amongst multiple providers, likely because it was present in an early version of the kubebuilder templates.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
To confirm that the removed configuration was redundant:
make release-manifestsout/infrastructure-components.yamlto /tmpmake release-manifestsagainRelease note: