KIP currently has issues with running in v1.21.x kubernetes cluster, because since v1.21.0 BoundServiceAccountTokenVolume feature gate is enabled by default, as it reached beta.

This result in KIP failure, due to fail in init container. If we patch service account token manually to the kip container, then it fails during creation of the pod.

To reproduce this bug create minikube cluster with BoundServiceAccountTokenVolume enabled minikube start --feature-gates=BoundServiceAccountTokenVolume=true.