Skip to content
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.

Restrict permissions for the server-acl-init job #454

Merged
merged 1 commit into from
May 12, 2020

Conversation

ishustava
Copy link
Contributor

Now that the server-acl-init command takes server DNS names as input, we don't need permissions to list pods and get statefulsets.

Additionally, only set one of connectInject.enabled to true in the generated config for HCS since we don't recommend enabling both connectInject and syncCatalog.

Now that the server-acl-init job takes server DNS names as input,
we don't need permissions to list pods and get statefulsets.

Additionally, only set one of connectInject.enabled to true
in the generated config for HCS
since we don't recommend enabling both connectInject and syncCatalog.
@ishustava ishustava added area/acls Related to ACLs area/chart-only Related to changes that simply require yaml chart changes, e.g. exposing a new field labels May 12, 2020
@ishustava ishustava requested a review from a team May 12, 2020 19:59
Copy link
Member

@lkysow lkysow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good. I didn't test it.

@ishustava ishustava merged commit da373a3 into master May 12, 2020
@ishustava ishustava deleted the restrict-server-acl-init-role branch May 12, 2020 23:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/acls Related to ACLs area/chart-only Related to changes that simply require yaml chart changes, e.g. exposing a new field
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants