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

Daemonst removal of hardcoded runAsUser #429

Merged
merged 2 commits into from Apr 28, 2020

Conversation

NissesSenap
Copy link
Contributor

The current runAsUser := 1000 creates issues when running in OCP.
If we assume that the user is set to none root in our checks
we can just grab that user ID and use that in the DS that is created.
Still have the default value in there if we for some reason can't find the id of the current user.

This will also work with runAsUser set in a standard k8s env or just
running it as a container since we have set 999 as the default user in
the containers.

The current runAsUser := 1000 creates issues when running in OCP.
If we assume that the user is set to none root in our checks
we can just grab that user ID and use that in the DS that is created.

This will also work with runAsUser set in a standard k8s env or just
running it as a container since we have set 999 as the default user in
the containers.
Copy link
Collaborator

@2infinitee 2infinitee left a comment

Choose a reason for hiding this comment

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

This looks good. I was able to take the changes and apply a security context with specified user.

Copy link
Collaborator

@integrii integrii left a comment

Choose a reason for hiding this comment

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

Makes sense to me. Thanks as always NissesSenap!

@integrii integrii merged commit a74eb45 into kuberhealthy:master Apr 28, 2020
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.

None yet

3 participants