FAQ
1) What should I do if I find a Kubernetes API object is supported by multiple API groups?
You may encounter this scenario when upgrading your Kubernetes cluster and the higher Kubernetes version has deprecated some of the API groups.
For example, extensions/v1beta1/Ingress is entirely deprecated by networking.k8s.io/v1/Ingress in Kubernetes v1.22. You may find extensions/v1beta1/Ingress and networking.k8s.io/v1/Ingress both exist in your system when upgrading the Kubernetes cluster from v1.16 to v1.20.
In this case, you have to disable the API group extensions/v1beta1 to ensure the system use the API group networking.k8s.io/v1 that is supported by FortiADC Ingress Controller. After disabling the API group, the Kubernetes API server needs to be restarted to apply the changes.
Follow the steps below:
- Edit
/etc/kubernetes/manifests/kube-apiserver.yaml - Under spec.containers.command, add
--runtime-config=extensions/v1beta1=false - Restart the Kubernetes API Server using
systemctl restart kubelet.service
For more information on enabling/disabling deprecated API groups, see https://kubernetes.io/docs/reference/using-api/#enabling-or-disabling.