Skip to content
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

admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+ #818

Closed
sozercan opened this issue Sep 10, 2020 · 7 comments · Fixed by #1250
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@sozercan
Copy link
Member

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
we should move to admissionregistration.k8s.io/v1

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Gatekeeper version:
  • Kubernetes version: (use kubectl version):
@sozercan sozercan added the enhancement New feature or request label Sep 10, 2020
@maxsmythe
Copy link
Contributor

Do you know at which K8s version admissionregistration.k8s.io/v1 was introduced?

@sozercan
Copy link
Member Author

@brycecr brycecr added the good first issue Good for newcomers label Sep 10, 2020
@maxsmythe
Copy link
Contributor

Thanks!

We should move to v1 once support for v1.15 has sunset (not sure if it has or not), otherwise we will be breaking v1.15.

@sozercan
Copy link
Member Author

Both v1.15 and v1.16 is already sunset https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/

@maxsmythe
Copy link
Contributor

I mean in terms of versions GK supports

@ritazh
Copy link
Member

ritazh commented Sep 10, 2020

Gatekeeper supported kubernetes versions should follow Kubernetes upstream:
https://github.com/open-policy-agent/gatekeeper/blob/master/docs/Release_Management.md#supported-kubernetes-versions

@maxsmythe
Copy link
Contributor

Makes sense.

Practically speaking, Azure and GKE both still support creating v1.15 clusters (I haven't checked other cloud providers). Should we delay until v1.15 clusters have sunset in the wild to avoid breaking current users?

There shouldn't be any cost for waiting as K8s v1.22 won't be a thing for another ~1 year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants