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.

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

Explicitly create service account token for eso-vault-auth-token #620

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

larsks
Copy link
Member

@larsks larsks commented Dec 3, 2024

With newer versions of kubernetes/openshift, it is necessary to explicitly
request a long-lived token for service accounts 1.

@larsks larsks force-pushed the fix/eso-vault-auth-token branch from aee9a90 to 6f666fa Compare December 3, 2024 17:03
@naved001
Copy link
Contributor

naved001 commented Dec 3, 2024

@larsks how was the sa token created before this?

@larsks
Copy link
Member Author

larsks commented Dec 3, 2024

@naved001 prior to Kubernetes 1.24, when you create a serviceaccount, kubernetes would automatically create a matching Secret containing a long-lived service account token. For 1.24 and later, this secret is not created automatically.

It looks like OpenShift has adopted the same behavior with 4.16 and later.

For these newer releases, if you want a long lived token you have to explicitly request one. If you just need a temporary token, you should use the kubectl create token command.

@larsks larsks enabled auto-merge December 3, 2024 18:05
@larsks larsks merged commit 85a34a2 into OCP-on-NERC:main Dec 3, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants