m3db-operator is not compatible with kubernetes v1.22

[abdulmi]

• What version of the operator are you running? Please include the docker tag. If using master, please include the git
  SHA logged when the operator first starts.

latest master 9758b96

• What version of Kubernetes are you running? Please include the output of kubectl version.
  1.22

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4", GitCommit:"3cce4a82b44f032d0cd1a1790e6d2f5a55d20aae", GitTreeState:"clean", BuildDate:"2021-08-11T18:16:05Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.6", GitCommit:"07959215dd83b4ae6317b33c824f845abd578642", GitTreeState:"clean", BuildDate:"2022-03-30T18:28:25Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}

• What are you trying to do?
  Upgrading the kubernetes server from 1.21 to 1.22

• What did you expect to happen?
  The operator continues to work as expected

• What happened?
  The m3db-operator crashloops with the error below

{"level":"info","ts":"2022-06-09T15:22:11.678Z","msg":"using InCluster k8s config"}
{"level":"info","ts":"2022-06-09T15:22:11.680Z","msg":"starting Operator controller","controller":"m3db-cluster-controller"}
{"level":"fatal","ts":"2022-06-09T15:22:11.977Z","msg":"error running controller","error":"could not create or update CRD: error creating CRD 'm3dbclusters.operator.m3db.io': the server could not find the requested resource","errorVerbose":"the server could not find the requested resource\nerror creating CRD 'm3dbclusters.operator.m3db.io'\ncould not create or update CRD"}

Looking into this, I found out that the m3db-operator code uses a deprecated method as mentioned by the Deprecated API guide. Specifically at this linem3db-operator/crd.go at 01941360ac992fc2f9cce0b6a3383dbde8baf859 · m3db/m3db-operator, its using apiextensions.k8s.io/v1beta1, which according to the guide should be replaced with apiextensions.k8s.io/v1. I have a starter PR to fix this #321, but I still have to fix the spec validation since its using a library thats also dependent on the beta version of the API.

Just wanted to check, is it expected that the operator is not compatible after kubernetes 1.21 ?

[schallert]

Hey @abdulmi, thanks for your patience while we work on making the operator 1.22-compatible. We have some final testing to do, but believe the linked PR will get us there. I'll keep you posted!