Add SCC for clusterController on OpenShift #3730
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Currently OpenShift users can't add clusterController because of
W1108 14:19:26.493318 42854 warnings.go:70] would violate PodSecurity "restricted:v1.24": hostPort (container "kubecost-cluster-controller" uses hostPort 9731), allowPrivilegeEscalation != false (container "kubecost-cluster-controller" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "kubecost-cluster-controller" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "kubecost-cluster-controller" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "kubecost-cluster-controller" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
Does this PR rely on any other PRs?
No
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Add SecurityContext for clusterController when it's enabled on OpenShift
Links to Issues or tickets this PR addresses or fixes
https://kubecost.atlassian.net/browse/SUP-6255
What risks are associated with merging this PR? What is required to fully test this PR?
Minimal risks.
How was this PR tested?
Manually
Have you made an update to documentation? If so, please provide the corresponding PR.
N/A