EKS 1.19 compatibility admissionregistration.k8s.io/v1beta1/ValidatingWebhookConfiguration

[awoimbee]

This doesn't work with kubernetes 1.19 (helm chart 1.1.5 -> aws-load-balancer-controller v2.1.3)

 error: apiVersion "admissionregistration.k8s.io/v1beta1/ValidatingWebhookConfiguration" was removed in Kubernetes 1.19. Use "admissionregistration.k8s.io/v1/ValidatingWebhookConfiguration" instead.
    See https://git.k8s.io/kubernetes/CHANGELOG/CHANGELOG-1.19.md#deprecation-1 for more information.

[M00nF1sh]

@awoimbee
We tested on our 1.19 EKS cluster, it's a warning instead error, and "deprecated" instead of "removed" in our case.

W0224 14:17:40.855650   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
W0224 14:17:40.901188   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
W0224 14:17:41.126371   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
W0224 14:17:41.145256   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration

wondering what could caused the behavior you saw in your case.
/kind investigation.

Also, i think it's time to vend YAMLs for different k8s versions anyway given it's a deprecated API.

[k8s-ci-robot]

@M00nF1sh: The label(s) kind/investigation. cannot be applied, because the repository doesn't have them

In response to this:

@awoimbee
We tested on our 1.19 EKS cluster, it's a warning instead error, and "deprecated" instead of "removed" in our case.

W0224 14:17:40.855650   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
W0224 14:17:40.901188   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
W0224 14:17:41.126371   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
W0224 14:17:41.145256   54224 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration

wondering what could caused the behavior you saw in your case.
/kind investigation.

Also, i think it's time to vend YAMLs for different k8s versions anyway given it's a deprecated API.

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/test-infra repository.

[M00nF1sh]

This is actually a bug in pulumi. the API removal is postponed to v1.22.
Upgrade to latest pulumi should fixed it:
pulumi/pulumi-kubernetes#1474
pulumi/pulumi-kubernetes#1475

[awoimbee]

I indeeed use pulumi. I didn't think it would have any impact on this issue
Thanks for the quick response !