Upgrade usage of deprecated APIs removed in k8s 1.22

[rifelpet]

/kind feature

1. Describe IN DETAIL the feature/behavior/change you would like to see.

https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22

In order to support k8s 1.22, kops will need to update its usage of deprecated APIs that have been removed in k8s 1.22.

We first discovered this in testing the aws-load-balancer-controller.

Most of the changes would be in addon manifests, but dns-controller (Ingress v1beta1) and protokube (RBAC v1beta1) will need updates as well. There may be other areas of the code base that I missed in my quick scan.

A few challenges we'll run into:

• Many of the replacement APIs were introduced in k8s versions newer than what is planned to be supported by kops 1.22. We'll have to decide whether to handle both API versions or narrow the support window for kops 1.22.
• Many of the addon manifests come from upstream, so we should work with them to get their manifests updated, but we'll also need to decide what to do if their manifests and/or client code arent updated by the time we intend to release kops 1.22.

[rifelpet]

Occurrences of API versions removed in 1.22:

apiextensions.k8s.io/v1beta1

• AWS VPC CNI: Deprecate v1beta1 for CRD eniconfig aws/amazon-vpc-cni-k8s#1534
• AWS IAM Authenticator: Upgrade the iamidentitymappings CRD to support apiextensions.k8s.io/v1 kubernetes-sigs/aws-iam-authenticator#384
• Canal
• CoreDNS

extensions/v1beta1

• dns-controller: Update dns-controller to use networking.k8s.io/v1 Ingress API #12119
• aws-load-balancer-controller: Migrate to networking.k8s.io/v1 Ingress API kubernetes-sigs/aws-load-balancer-controller#2050 (comment)

rbac.authorization.k8s.io/v1beta1

• kopeio: Update addon manifests referencing RBAC v1beta1 #12120
• AWS IAM Authenticator

[johngmyers]

We've added validation for those components which use APIs removed in k8s 1.22. When any of those update, we can remove the corresponding validation and cherry-pick to release-1.22.

Nothing else to track here.
/close

[k8s-ci-robot]

@johngmyers: Closing this issue.

In response to this:

We've added validation for those components which use APIs removed in k8s 1.22. When any of those update, we can remove the corresponding validation and cherry-pick to release-1.22.

Nothing else to track here.
/close

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.

[gtorre]

@johngmyers @rifelpet I believe aws load balancer controller has been updated, see kubernetes-sigs/aws-load-balancer-controller#2433

Are there plans to remove the validation? Is there a way to get around this if I'm currently using aws load balancer controller but want to upgrade to v1.22?

[olemarkus]

We're still waiting for a release with that fix. should arrive in the near future. We'll remove the validation then.

[gtorre]

Thank you @olemarkus !