Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't access ClusterServiceVersions on non OpenShift cluster

See original GitHub issue

Describe the bug

In order to list operators installed on a cluster, we should use the operators.coreos.com/v1alpha1:ClusterServiceVersion.

This resource is available through OpenShiftOperatorHubAPIGroupDSL. But this one is available through the OpenShiftClient.

But this resource is available on raw Kubernetes cluster once you installed the Operator Lifecycle Manager.

So today it is possible only if user uses OpenShiftOperatorHubAPIGroupClient passing the Kubernetes client as a parameter which I’m not sure is a public supported API

Fabric8 Kubernetes Client version

5.12.4

Steps to reproduce

See https://github.com/redhat-developer/intellij-openshift-connector/pull/484/files#diff-e332bfa50ae6e995739ad7ae9869734c6299f0d4286bf72d9fc3876207fe89fbR485

Expected behavior

Should be possible to adapt KubernetesClient to OpenShiftOperatorHubAPIGroupDSL

Runtime

Kubernetes (vanilla)

Kubernetes API Server version

1.23

Environment

Windows

Fabric8 Kubernetes Client Logs

No response

Additional context

No response

Issue Analytics

State:
Created 10 months ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

jeffmaurycommented, Nov 28, 2022

I need a typed access to this resource so I found another workaround

0reactions

jeffmaurycommented, Dec 13, 2022

I need a typed access to this resource so I found another workaround

What was the other workaround?

Not sure what your workaround was. Here is another suggestion:

If the model is in a separate module, add the dependency to that module and then register the model in the KubernetesDeserializer.

See https://github.com/redhat-developer/intellij-openshift-connector/pull/484/files#diff-e332bfa50ae6e995739ad7ae9869734c6299f0d4286bf72d9fc3876207fe89fbR513

Top Results From Across the Web

OpenShift cluster will not recognize the new operator versions ...

Issue. We are trying to upgrade an operator to a higher version, but the installation is looking for a lower version; For example, ......

Troubleshooting Operator issues - OpenShift Documentation

Accessing cluster nodes using SSH is not recommended and nodes will be tainted as accessed. However, if the OpenShift Container Platform API ...

Unable to update Red Hat OpenShift Container Platform ... - IBM

Unable to update Red Hat OpenShift Container Platform cluster to 4.10 ... not be upgraded between minor versions: ClusterServiceVersions blocking cluster ...

Deploy Project Quay on OpenShift with the Quay Operator

Ensure your OpenShift cluster has sufficient compute resources for these requirements. ... {"message":"Cannot initialize user in a non-empty database"}.

What are Operators in Kubernetes or OpenShift? - marukhno

They work in a non-terminating loop compare controled component's current ... cluster instead of the single Pod I cannot just scale it up....