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

SCC for daemonset not integrated with openshift operator bundle #227

Open
cpmeadors opened this issue Nov 5, 2024 · 2 comments
Open

SCC for daemonset not integrated with openshift operator bundle #227

cpmeadors opened this issue Nov 5, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@cpmeadors
Copy link
Contributor

the SCC and rbac configuration from these files are needed to allow the daemonset to start on and OpenShift cluster.

config/rbac/instaslice-operator-scc.yaml
config/rbac/openshift_cluster_role.yaml
config/rbac/openshift_scc_cluster_role_binding.yaml

This is usually done by adding them to the config/rbac/kustomization.yaml file which causes them to be rendered into the CSV of the bundle. This has been tested and worked but instaslice-operator-scc.yaml still needed to be applied manually.

@cpmeadors
Copy link
Contributor Author

https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/ provides some guidance on how this is supposed to be done.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants