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

Kratos Courier Stateful set doesn't include the ServiceAccountName #434

Closed
5 of 6 tasks
adamstrawson opened this issue Apr 22, 2022 · 0 comments · Fixed by #435
Closed
5 of 6 tasks

Kratos Courier Stateful set doesn't include the ServiceAccountName #434

adamstrawson opened this issue Apr 22, 2022 · 0 comments · Fixed by #435
Labels
bug Something is not working.

Comments

@adamstrawson
Copy link
Contributor

Preflight checklist

Describe the bug

The Kratos deployment includes a ServiceAccountName for the SA it creates, however this isn't included in the courier pods.

This causes kratos-courier to fail to start when using with extraContainers that require elevated permissions defined by the ServiceAccount.

Reproducing the bug

No steps required. Missing configuration.

Relevant log output

No response

Relevant configuration

No response

Version

kratos-0.23.1

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant