Challenged with `certificates.k8s.io/v1` about akri-webhook HOT 4 OPEN

I think your issue can be solved by limiting the usages. I don't know your usage but I got the same "Approved, Failed" issue. I solved it by limiting the usage to "- client auth" which in my case fits the purpose. Now, I got:
# kubectl get csr NAME AGE SIGNERNAME REQUESTOR CONDITION cilentname 10m kubernetes.io/kube-apiserver-client kube-admin Approved,Issued

from akri-webhook.

Thank you @ghakfoort, I gave up on using the API Server and used cert-manager.io but, I'll try your solution too as there are less moving parts.

from akri-webhook.

Cool. Let me know if it works. I did several other things but you said it worked with the v1beta1 so I did not mention it.

from akri-webhook.

Thank you for the v1beta1 suggestion!

I'm having this issue as well, and I don't feel like the v1beta1 with kubernetes.io/legacy-unknown is a great long-term (production) solution. It seems that to support cert signing for v1 we would have to do the following:

1. Add the cluster-signing-key-file and cluster-signing-cert-file parameters to the kube-controller manager (I did this in my clusterconfiguration file when standing up the cluster) https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/#a-note-to-cluster-administrators
2. Create RBAC policies for a certificate controller (https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/#authorization)
3. Listen to events and respond to the custom signerName label

I haven't really gone too far down this because its a lot of work when I can just switch to the v1beta1 version of CSR, but wanted to get the opinion of others.

from akri-webhook.