Upgrade the iamidentitymappings CRD to support apiextensions.k8s.io/v1

[arruko]

What happens?

The iamidentitymappings CRD was created with version apiextensions.k8s.io/v1beta1 of the api, which means that after version 1.22 of Kubernetes it can no longer be used.

Expecting to happen

Both kubernetes resources (including CRD) and aws-iam-authenticator source code supports version apiextensions.k8s.io/v1

The main problem is that after reviewing the code I see that the golang v1alpha1 kubernetes api package is widely used, so I would like to know what is your feedback on this change. If it doesn't affect anything other than the CRD I'd be happy to collaborate with a solution.

Logs

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Versions of software

Toolchain Version:
Kubernetes: v1.22.0-beta.0

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[rifelpet]

/remove-lifecycle stale