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

Gatekeeper should not use the default ServiceAccount #356

Closed
maxsmythe opened this issue Dec 18, 2019 · 2 comments · Fixed by #431
Closed

Gatekeeper should not use the default ServiceAccount #356

maxsmythe opened this issue Dec 18, 2019 · 2 comments · Fixed by #431
Assignees
Labels
good first issue Good for newcomers

Comments

@maxsmythe
Copy link
Contributor

Because the Gatekeeper service account requires so many permissions, it should have a separate service account in the namespace to prevent other pods from having equivalent access.

@maxsmythe maxsmythe added the good first issue Good for newcomers label Dec 18, 2019
@maxsmythe maxsmythe changed the title Gatekeeper should not use the default serviceaccount Gatekeeper should not use the default ServiceAccount Dec 18, 2019
@EmandM
Copy link
Contributor

EmandM commented Jan 17, 2020

I can take this one

maxsmythe added a commit that referenced this issue Jan 22, 2020
… (#431)

* Use a designated ServiceAccount instead of the namespace default

Signed-off-by: Emma McMillan <emma.mcmillan@microsoft.com>

* Apply service account to gatekeeper Pod

Signed-off-by: Emma McMillan <emma.mcmillan@microsoft.com>

* Add manifest_staging changes

Signed-off-by: Emma McMillan <emma.mcmillan@microsoft.com>

Co-authored-by: Max Smythe <max.smythe@gmail.com>
@maxsmythe
Copy link
Contributor Author

Fixed in #431

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants