-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🐛 (kustomize/v2,go/v4): fix uncomment kustomize files config accordinly when webhooks are generate #3629
🐛 (kustomize/v2,go/v4): fix uncomment kustomize files config accordinly when webhooks are generate #3629
Conversation
f3233cf
to
a910425
Compare
- path: patches/webhook_in_ship_destroyers.yaml | ||
- path: patches/webhook_in_ship_cruisers.yaml | ||
- path: patches/webhook_in_sea-creatures_krakens.yaml | ||
- path: patches/webhook_in_sea-creatures_leviathans.yaml | ||
#- path: patches/webhook_in_foo.policy_healthcheckpolicies.yaml |
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.
The root cause here seems unrelated to the scope of this PR : #3630
Those that are not comment is because where created with the command create api when they should not be created in the first place.
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.
Hi @Sajiyah-Salat,
Also, as you have said, the issue is out of the scope of this PR. Could you let me know what we can address in a follow-up PR?
Regards: PR Discussion
In the sample project which is using a multi-group layout, we can see that some patches were not uncommented.
Why does this happen?
Because those patches should not exist in the first place.
They have been created when we run create api
, but should only be created in specific scenarios, those when we run webhook create
. The change of this PR is in the webhook subcommands, therefore, it is not reflected in this case scenario.
However, since the bug found is not part of the context of this PR, I would like to refer to the issue created. I think there is a better place to discuss this. #3630
I understood the issue. Can you please let me know how can I test this changes and know more about it. Also as you have said the issue is out of scope of this pr. So could you let me know what we can do in follow up pr. |
Hi @Sajiyah-Salat,
The goal of this PR is to uncomment the kustomize files to enable webhooks when webhooks are scaffolded (
See; #3629 (comment) |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, varshaprasad96 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 |
Description
We should NOT let the webhook configuration be commented on when a webhook is created. Therefore, this PR ensures that when we run kubebuilder to create a webhook we will uncomment the required places under the config so that webhooks are enabled by default.