Drop SeccompProfile from populator pod #211
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
Having the SeccompProfile set to runtime caused an issue starting the pod. Signed-off-by: Liran Rotenberg <[email protected]>
|
Kudos, SonarCloud Quality Gate passed!
|
ahadas
approved these changes
Mar 9, 2023
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #211 +/- ##
==========================================
- Coverage 33.94% 30.55% -3.40%
==========================================
Files 43 45 +2
Lines 8112 9250 +1138
==========================================
+ Hits 2754 2826 +72
- Misses 5141 6201 +1060
- Partials 217 223 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Having the SeccompProfile set to runtime caused an issue starting the pod with the error:
E0308 21:59:06.167954 1 controller.go:418] error syncing 'pvc/arik/2d096ab7-44fa-4935-b0d0-333532e84e5f': pods "populate-f4436d1b-2075-4a51-b6a1-3b1d72e29cde" is forbidden: unable to validate against any security context constraint: [pod.metadata.annotations[[container.seccomp.security.alpha.kubernetes.io/populate](http://container.seccomp.security.alpha.kubernetes.io/populate)]: Forbidden: seccomp may not be set, provider "containerized-data-importer": Forbidden: not usable by user or serviceaccount, provider restricted-v2: .spec.securityContext.fsGroup: Invalid value: []int64{107}: 107 is not an allowed group, spec.containers[0].securityContext.runAsUser: Invalid value: 107: must be in the ranges: [1000700000, 1000709999], provider "restricted": Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "kubevirt-controller": Forbidden: not usable b...That came from PR #189 and relates to openshift/cluster-kube-apiserver-operator#1325