-
Notifications
You must be signed in to change notification settings - Fork 83
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
Helm chart: Own service accounts for API and Web #621
Helm chart: Own service accounts for API and Web #621
Conversation
LGTM (tested on our setup) except the fact that I think you should not bump the helm chart version manually as it's handled by the CI but maybe @garronej can enlighten us on this ? |
Service account was previously specified at root level. When using serviceAccount.create, this was OK, since api and web would then get their own SAs. When serviceAccount.create was false however, the same SA would be used for both api and web, which is very problematic of several reasons. This commit fix this issue by moving the serviceAccount field from root to both api and web. This also make it clearer what happen under-the-hood. The change is breaking, and major version is therefore bumped.
0381302
to
d4bc723
Compare
Thanks, @olevitt . Rebased on main now and reverted bump of chart version. |
@johnksv Thanks a lot for this PR!
@olevitt @johnksv, You did good by bumping the Helm chart version to the next major. The deployment workflow automatically bump the chart when there is a bump on either -web or -api but you can also pub the helm chart version manually, this too will triger a release. Regarding the update of the docs.onyxia.sh website, there's two approach.
Thanks again for your contribution. |
OK, I'll bump the chart version again, and write some doc (got your invitation) |
Added a "change request" in gitbook, @garronej . Feel free to edit the docs (and this PR of course) accordingly |
Sorry for the delay, I'll fix the conflict and merge asap |
See issue #616 which this PR resolves.
Question: Where should i update the doc (as this is a breaking change)?
PS: I have not had the opportunity to test this yet, but wanted to create the PR such that it can be discussed.
Commit message describing the change:
Service account was previously specified at root level. When using serviceAccount.create, this was OK, since api and web would then get their own SAs. When serviceAccount.create was false however, the same SA would be used for both api and web, which is very problematic of several reasons.
This commit fix this issue by moving the serviceAccount field from root to both api and web. This also make it clearer what happen under-the-hood.
The change is breaking, and major version is therefore bumped.