Closed abergmeier closed 4 years ago
The OpenShift 3.11 will use a k8s API which is no longer supported after the 0.9 version of SDK. Then, issues also can be faced. Could you please check it in the Minikube and/or OCP 4.X which will use API compatible versions and let us know if you still facing the same issue?
@abergmeier That's a interesting error message. If you Google "unable to validate against any security context constraint", you get a bunch of results where the brackets have some clue about what's wrong. In your case, it's totally empty. Not sure how that happens.
I would agree with @camilamacedo86 that the version skew between Operator SDK 0.12 (which uses kubernetes 1.15 client libraries) and your cluster may be an issue. It would be helpful to know if you experience the same issue on a more recent cluster.
I know controllerutils.CreateOrUpdate
is doing quite a bit under the hood. But any chance you could debug more and figure out exactly which call to the API server is causing this error? It seems like it's probably a write (e.g. creating or updating the pod), but it would be good to know for sure.
@abergmeier Hopefully you solved your problem, but if not let us know and we can re-open to continue troubleshooting!
Bug Report
When upgrading our working Operator from 0.11 to 0.12, we get an error:
Our Operator tries to deploy a Pod named
bar-pod
usingcontrollerutil.CreateOrUpdate
.What did you do?
Deployed our Operator using SDK 0.12.
What did you expect to see?
Should just reconcile fine.
Environment
Kubernetes cluster kind: The operator is running on OpenShift 3.11.
Are you writing your operator in ansible, helm, or go? go