Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KIP does not support BoundServiceAccount Token Volume #238

Open
hidalgopl opened this issue May 21, 2021 · 0 comments
Open

KIP does not support BoundServiceAccount Token Volume #238

hidalgopl opened this issue May 21, 2021 · 0 comments
Labels
bug Something isn't working conformance

Comments

@hidalgopl
Copy link
Contributor

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.
@hidalgopl hidalgopl added bug Something isn't working conformance labels May 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working conformance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hidalgopl