We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In order to support Windows system, we should add rego rules to check for securityContext parameters also for this OS. Reading from the official documentation, we should implement a control for each of the following listed fields: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#windowssecuritycontextoptions-v1-core So, the new checks to be added, are the following:
securityContext
gmsaCredentialSpec
gmsaCredentialSpecName
hostProcess
runAsUserName
The equivalent rules should be named like so:
set-gmsacredentialspec-value
set-gmsacredentialspecname-value
set-hostprocess-true
WindowsHostProcessContainers
api-server
The text was updated successfully, but these errors were encountered:
@0xquark can this issue be of your interest?
Sorry, something went wrong.
Yes! Seems like a good addition
No branches or pull requests
In order to support Windows system, we should add rego rules to check for
securityContext
parameters also for this OS.Reading from the official documentation, we should implement a control for each of the following listed fields: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#windowssecuritycontextoptions-v1-core
So, the new checks to be added, are the following:
gmsaCredentialSpec
gmsaCredentialSpecName
hostProcess
runAsUserName
The equivalent rules should be named like so:
set-gmsacredentialspec-value
set-gmsacredentialspecname-value
set-hostprocess-true
(checking also ifWindowsHostProcessContainers
feature flag is enabled inapi-server
)runAsUserName
The text was updated successfully, but these errors were encountered: