-
Notifications
You must be signed in to change notification settings - Fork 17
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
check-compliance-policy and check-imagie-FIPS added #188
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: sratslla <[email protected]>
template: | ||
spec: | ||
containers: | ||
- name: discovery |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the container name guaranteed to be discovery?
kinds: | ||
- Deployment | ||
namespaces: | ||
- istio-system |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should also add the match for istiod
Deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also maybe a good idea to write the check for Pod instead
- resources: | ||
kinds: | ||
- Pod | ||
- Deployment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably write the check only for Pod
. Other controllers will be handled by auto-gen rules.
I will fix these and add the rest of the policies I have been working on in this PR by EOD. |
check-compliance-policy and check-imagie-FIPS-compliant added