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

Fix | 2022.4 | Server/Gateway: pre-existing service account name is ignored by Gateway chart in custom namespaces #641

Merged
merged 1 commit into from
Aug 22, 2022

Conversation

andreazorzetto
Copy link
Contributor

This change fixes an issue that causes the wrong service account to be assigned to the gateway under these circumstances:

  • server chart is used to deploy server and gateway
  • charts are installed into custom namespace
  • serviceAccount.create=false and gateway.serviceAccount.create=false

The specific issue with the current chart is that the gatway will not receive the service account name and in the deployment manifest will assign "namespace-sa" service account to the gateway. This results in a gateway pod not starting

… gateway under these circumstances:

- custom namespace used
- service account create set to false for the server chart
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@semyonmor semyonmor merged commit 046a9db into aquasecurity:2022.4 Aug 22, 2022
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.

4 participants