Operator versions compatible with

Support
#1

Hi there,

Currently I run pulp-operator.v1.0.0-beta.4(with frozen pulpcore 3.96 due to know Django related issue - https://github.com/pulp/pulp-operator/issues/159) on Openshift 4.16(compatible with 1.29 k8s version). I want to migrate to stable channel, but on operatorhub all stable versions(1.0.0 - 1.3.0 and 2.0.0) require kubernetes 1.30.0. And for now I can’t upgrade the Openshift cluster.

Are some 1.30 specific kubernetes APIs used starting from 1st stable operator version? Or are there any other reasons why 1.30 is required for this?

Thanks in advance.

#2

Hi @aisachenka

Sorry for the delayed response!

Are some 1.30 specific kubernetes APIs used starting from 1st stable operator version? Or are there any other reasons why 1.30 is required for this?

The stable versions are not using any APIs introduced in k8s 1.30 or later.
We changed the k8s version requirements to match/align with the versions we run in our CI tests.

2 Likes
#3

Thanks for the answer @hyagi.
Can then minKubeVersion be changed in ClusterServiceVersion to be able to install it via OLM?
If not, Is the helm only possible way to install Pulp operator then?

#4

Can then minKubeVersion be changed in ClusterServiceVersion to be able to install it via OLM?

Hm… I think to do that you would need to regenerate the bundle with the modified CSV.

If not, Is the helm only possible way to install Pulp operator then?

You can also install it from source: Quickstart with Kubernetes - Pulp Project
Basically, you would need to:

  • clone operator’s repo
    git clone https://github.com/pulp/pulp-operator ; cd $_

  • provision the operator as a k8s deployment
    NAMESPACE=my-pulp-namespace make deploy

OR for development or testing purposes, you could also run the operator from go source:

  • clone operator’s repo
    git clone https://github.com/pulp/pulp-operator ; cd $_

  • run it
    WATCH_NAMESPACE=my-pulp-namespace go run main.go