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

Always create sshPortal authorization resources and add a service account token resource #607

Closed
wants to merge 1 commit into from

Conversation

rocketeerbkw
Copy link
Member

In order to keep the legacy SSH service in lagoon-core working in recent k8s clusters, a non-expiring token is needed. A sufficiently scoped role and binding already exists for the ssh-portal, so this PR adds the service account token secret that can be used in lagoon-core. Since this is needed even if ssh-portal isn't used, the auth related resources are changed to always be created, even if the ssh-portal service isn't enabled.

@smlx
Copy link
Member

smlx commented Sep 8, 2023

The documentation for the k8s API used in this PR is here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#manually-create-an-api-token-for-a-serviceaccount

Could we put the creation of this secret behind a flag so that people have to understand the step they are taking with this? e.g. maybe a top-level createLegacySSHServiceAccountToken: false in the values file with an explanatory comment?

@rocketeerbkw
Copy link
Member Author

Superseded by #608

@rocketeerbkw rocketeerbkw deleted the ssh-portal-serviceaccount-token branch September 12, 2023 21:59
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.

2 participants