Skip to content
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

Provider "scanner": Forbidden: not usable by user or serviceaccount #636

Closed
rkrbaddam opened this issue May 8, 2024 · 1 comment
Closed

Comments

@rkrbaddam
Copy link

Hello Team

Can you please help me on below

I'm currently implementing Cloud Native Feature-Flagging using the OpenFeature Operator.

I've followed all the steps outlined in https://openfeature.dev/docs/tutorials/ofo to install the OpenFeature Operator in our OCP cluster.

The only deviation is that instead of using the demo-app workload provided in end-to-end.yaml, I'm utilizing my own Spring Boot Java deployment. I've added the following annotations to configure flagD as a sidecar:

annotations:
openfeature.dev/enabled: 'true'
openfeature.dev/featureflagsource: flag-sources

However, we're encountering the following error after adding the annotations:

pods "********" is forbidden: unable to validate
against any security context constraint: [provider "scanner": Forbidden:
not usable by user or serviceaccount, provider "anyuid": Forbidden: not
usable by user or serviceaccount, provider nfs-scc:
.containers[1].runAsUser: Invalid value: 65532: must be in the ranges: [**********, **********]
pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/flagd]:
Forbidden: seccomp may not be set, --------------------

@beeme1mr
Copy link
Member

beeme1mr commented May 8, 2024

Hey @rkrbaddam, it looks like your OCP cluster has a security context constraint that doesn't allow the image to run using the default non-root user. Here is where we're setting the user and group. Please either update your security policy to allow a container to run as 65532.

@beeme1mr beeme1mr closed this as completed Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants