| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Skipping CI for Draft Pull Request. |
Sorry, something went wrong.
|
[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. Details Needs approval from an approver in each of these files:Approvers can indicate their approval by writing /approve in a comment |
Sorry, something went wrong.
| } | ||
|
|
||
| ingressClass := &networkingv1.IngressClass{} | ||
| // TODO: How do we deal with 404s? The ingress class might be created just moments later. |
There was a problem hiding this comment.
It is not ideal that we do a lookup here that might fail.
Alternatively, we could also check stackit.cloud annotations regardless of the ingress class. However, we can't validate missing required annotations that way.
Sorry, something went wrong.
|
Our project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
Sorry, something went wrong.
|
/lifecycle frozen |
Sorry, something went wrong.
|
@dergeberl: The lifecycle/frozen label cannot be applied to Pull Requests. 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. |
Sorry, something went wrong.
|
PR needs rebase. 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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
How to categorize this PR?
/kind enhancement
What this PR does / why we need it:
When the controller receives an invalid object it either needs to discard it or stop reconciliation altogether. A webhook can catch invalid objects during admission.