Open cpmeadors opened 2 weeks ago
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.
https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/ provides some guidance on how this is supposed to be done.
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.