Operator projects using the removed APIs in k8s 1.22 requires changes.

[storageos]

Operator projects using the removed APIs in k8s 1.22 requires changes.

[croomes]

Hi, we're replacing this project with https://github.com/storageos/operator which is compatible with v1.22. We should be releasing it soon.

[ukd1]

Just hit this running 1.22 - not a great first time user experience:

k  create -f https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml
namespace/storageos-operator created
clusterrole.rbac.authorization.k8s.io/storageos-operator created
serviceaccount/storageoscluster-operator-sa created
deployment.apps/storageos-cluster-operator created
unable to recognize "https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "https://github.com/storageos/cluster-operator/releases/download/v2.4.4/storageos-operator.yaml": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"

[ukd1]

@croomes all your public docs point to this repo, and 1.22 has been out since early August, and these have been throwing warnings before they were removed. This wasn't / is not ideal first-time user experience for me, and I'm surprised.

[camilamacedo86]

Hi, would we have any update on this?

See that we are very close to the release data and fix the projects seems not very hard. See how to fix it in the first comment. Then, would be great to be able to check a new version of your project distributed which is compatible with 4.9.

[camilamacedo86]

HI croomes,

Could you make that clear in the Readme of this project and also if possible a description of your operator into the catalog? How your users will be aware of it?

Have you been distributing the other project on OCP? if yes, could you also publish compatible versions?

[camilamacedo86]

Hi @croomes ,

Be aware that: if you do not provide a workable solution via RedHat Connect asap:

• Your package/project will be removed from 4.9 catalog
• You cannot use replaces in your first publication made to add the project again on 4.9 when you publish the compatible version
• Your users cannot upgrade their cluster to use 4.9 with your solution installed then, they will need to stick on 4.8 or stop using your project to be able to move forward.

I would recommend you try to prioritize this one.

[croomes]

Hi @camilamacedo86, we are very close to releasing StorageOS v2.5.0 which is based on the new operator at https://github.com/storageos/operator. It is currently in beta.

How long do we have to release it before we're removed from the catalog?

cc @actionbuddha

[camilamacedo86]

Hi @croomes,

Hi @camilamacedo86, we are very close to releasing StorageOS v2.5.0 which is based on the new operator at https://github.com/storageos/operator. It is currently in beta.

A project that does not exist now in 4.9 pre-ga indexes cannot be removed. So, for the new project that does not apply at all.

How long do we have to release it before we're removed from the catalog?

This issue is about storageos2 package. This package has no compatible/workable solutions on 4.9 and then, before the 4.9 release, it will be removed from 4.9 if not provide any valid version with.

According to the https://connect.redhat.com/blog/api-deprecation-kubernetes-122-will-impact-your-operators you had up Sep 30. This time was extended until the latest Friday.

Note that you can always send new versions compatible with 4.9. However, the limitation here is that you will be unable to use replaces to publish in 4.9 and below. So, the easy way would be to publish asap a compatible version with 4.9 via RedHat Connect if you would like to still distribute solutions for the package storageos2.

[croomes]

@camilamacedo86 we'd planned to push the new operator (https://github.com/storageos/operator) to the operator2 package rather than creating a new project. We should be able to do this by the end of the week.

Hopefully that's the best approach?

[camilamacedo86]

HI @croomes,

Be aware that your first publication targeting OCP 4.9 (if not get in time) you cannot use the “replaces” configuration since any previous version published so far does not exist on 4.9 to be replaced. You can publish your new distribution using the skips or skipRange options instead of replaces. More info: https://v0-18-z.olm.operatorframework.io/docs/concepts/olm-architecture/operator-catalog/creating-an-update-graph/. If you have been using replaces I'd try to suggest you push asap.

All please see https://connect.redhat.com/blog/api-deprecation-kubernetes-122-will-impact-your-operators.