Disable seccomp checking in CI (kubeaudit) #119
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I updated the security configurations in the following PR.
#118
Now, in the Scalar Helm Charts, we use
securityContext.seccompProfileinstead ofseccomp.security.alpha.kubernetes.io/podannotation. This is because this annotation is deprecated now and it will be removed in the next kubernetes release.However, the
kubeauditreturns error as a result ofseccompchecking since thekubeauditdoes not understandPodSecurityContext.seccompProfile.This is a known issue in the
kubeaudit.Please see the following comment too.
#118 (comment)
So, I updated the configuration of
kubeauditto disableseccompchecking.We can enable it again after the known issue of
kubeauditwill be fixed.Please take a look!