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

Unable to configure ServiceAccountName using Kamel run #3797

Closed
Thomas9047 opened this issue Nov 7, 2022 · 2 comments · Fixed by #4030
Closed

Unable to configure ServiceAccountName using Kamel run #3797

Thomas9047 opened this issue Nov 7, 2022 · 2 comments · Fixed by #4030
Assignees
Labels
area/traits good first issue Does not require full understanding of the codebase kind/feature New feature or request

Comments

@Thomas9047
Copy link

Hello all,

First of all, I hope that this is the correct place.
I am trying to configure the ServiceAccountName for an integration.
I have looked at the following issue: #305, but I can't find any documentation for this.

Is there an option to set the serviceAccountName using Kamel run? Maybe by using a pod trait?

Thanks in advance

@tadayosi
Copy link
Member

tadayosi commented Nov 8, 2022

Right now you'd need to manually modify the Integration CR to apply the serviceAccountName parameter, e.g.:

kubectl patch it <your-integration> -p '{"spec": {"serviceAccountName": "CUSTOM_SERVICE_ACCOUNT" }}'

@squakez
Copy link
Contributor

squakez commented Nov 15, 2022

Definitely it would be a good idea for a new trait. Feel free to contribute to it!

@squakez squakez added kind/feature New feature or request good first issue Does not require full understanding of the codebase labels Nov 15, 2022
@squakez squakez self-assigned this Feb 3, 2023
@squakez squakez mentioned this issue Feb 3, 2023
squakez added a commit to squakez/camel-k that referenced this issue Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/traits good first issue Does not require full understanding of the codebase kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants