Crate Operator on OpenShift not working

FrancescoL96 · March 11, 2025, 12:39pm

I am having issues with the crate-operator on an openshift cluster, I have detailed the problem on a github issue:

Crate Operator on OpenShift

opened 12:31PM - 11 Mar 25 UTC

triage

Hello! I am trying to use the Crate Operator on an OpenShift instance, similarly… to https://github.com/crate/crate-operator/issues/300, I had trouble with explicit permissions on finalizers. This was easiliy solved by updating the rbac. However, this still does not allow the operator to work. When creating a new instance through a custom resource, the operator logs the following message: ``` [2025-03-11 11:42:49,258] kopf.objects [INFO ] [krateo-system/finops-finops-cratedb-custom-resource] Trying to create system user ... [2025-03-11 11:42:49,271] kopf.objects [ERROR ] [krateo-system/finops-finops-cratedb-custom-resource] ... failed. Status: 404 Message: Invalid response status ``` This seems to be caused by this call in the [bootstrap](https://github.com/crate/crate-operator/blob/ae24778f403618d7dfce30fa7874d4b43d548fe1/crate/operator/bootstrap.py): https://github.com/crate/crate-operator/blob/ae24778f403618d7dfce30fa7874d4b43d548fe1/crate/operator/bootstrap.py#L129 which in turn calls this Kubernetes library: https://github.com/crate/crate-operator/blob/ae24778f403618d7dfce30fa7874d4b43d548fe1/crate/operator/bootstrap.py#L113 In the readme of https://github.com/RedHatQE/openshift-python-wrapper/, it explicitly states: ``` The wrapper also provides additional capabilities, such as resource-specific functionality that otherwise needs to be implemented by users. [...] One example of simplified usage is interacting with a container. Running a command inside a container requires using Kubernetes stream, handling errors, and more. The wrapper handles it all and provides simple and intuitive functionality. ``` which makes me assume that this is the root cause of this issue: OpenShift uses a different API to manage some objects, requiring different handling. I assume that a traditional deployment of CrateDB will work just fine on OpenShift (which is going to be what I will do now), however, this completely stops the operator from working in these types of clusters.

In short, OpenShift handles some objects differently from Kubernetes and it stops the operator from working.

Topic		Replies	Views
Crate version update in K8S not fully automated? CrateDB	0	45	March 11, 2025
Install the CrateDB k8s operator with Helm Community	0	549	October 3, 2022
How allowedCIDRs works? Installation	3	23	December 10, 2024
How to enable HBA when using crate-operator? Configuration	5	18	December 4, 2024
CrateDB does not select a leader CrateDB getting-started	5	323	October 6, 2023

Crate Operator on OpenShift not working

Related topics