-
Notifications
You must be signed in to change notification settings - Fork 472
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
fix: Add BackendLBPolicy to experimental kustomization #3083
Conversation
Kustomization does not install this new CRD because it is not on the list of resources.
The committers listed above are authorized under a signed CLA. |
Welcome @krouma! |
Hi @krouma. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
Thanks @krouma!
/approve
/ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krouma, robscott 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 |
/lgtm |
…gs#3083) Kustomization does not install this new CRD because it is not on the list of resources.
…gs#3083) Kustomization does not install this new CRD because it is not on the list of resources.
Kustomization does not install this new CRD because it is not on the list of resources.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes installation of experimental CRDs using kustomization.
Which issue(s) this PR fixes:
Does this PR introduce a user-facing change?: