-
Notifications
You must be signed in to change notification settings - Fork 880
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
Update mutating webhook API Version #408
Conversation
@lawliet89 Thanks! I think we should set it to |
@jasonodonnell I have set it to I also tried adding tests to see if we can test if the
|
9600e99
to
124ce31
Compare
I have also added new fields that are required for |
@jasonodonnell Could you review this again please? |
@lawliet89 looks good but I'm wondering if |
@lawliet89 I asked a similar question here: hashicorp/vault-k8s#168 |
I am not too familiar with the kubernetes api library. I'm not sure if a v1 api library function can work with v1beta1 endpoint. It's not quite the same change as this PR imo. |
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, tested out fine here.
admissionregistration.k8s.io/v1beta1
is deprecated since 1.16 and will be removed in 1.19.This PR will set the right API Version if it is supported.
However, there is a change in behaviour from
v1beta1
tov1
. Specifically, the default (unspecified)failurePolicy
changes fromIgnore
toFail
. Should we set the default invalues.yaml
toIgnore
to preserve the previous behaviour? Or this can be labelled a breaking change?