Microk8s implementation warnings and not starting pods

when i install the yaml via microk8s kubectl apply -f nri.yaml -n default i have the folowing warnings:

• Warning: rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
• Warning: admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
• Warning: rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding

And also the pod " nri-bundle-nri-metadata-injection-job " is giving the error “Error creating: pods “nri-bundle-nri-metadata-injection-job-” is forbidden: error looking up service account default/nri-bundle-nri-metadata-injection: serviceaccount “nri-bundle-nri-metadata-injection” not found”

how can i get it working?

Hi @mattijs.brunink, thanks for your question!

The warnings you see are related to the version of K8s that you’re running, you can remove the warning messages by changing rbac.authorization.k8s.io/v1beta1 to rbac.authorization.k8s.io/v1 in the ClusterRole, MutatingWebhookConfiguration and ClusterRoleBinding yaml files.

This error indicates that the “nri-bundle-nri-metadata-injection” serviceaccount cannot be found, it is possible that this was not successfully created. Could you check if this exists by running the following command:

kubectl get service account -n [namespace] nri-bundle-nri-metadata-injection