![]() Testing your changesĪfter you have packaged a new version, test out your Operator on both OpenShift 4.8 and if available, an OpenShift 4.9 release candidate. An example of this situation would be if you will also skip the distribution on the previous OCP version(s) and their specific constraints. If you are unable to solve this scenario by using these options due to a complex update graph, you will need to raise a ticket asking for manual intervention and we will help you out. To ensure an 4.8 to 4.9 upgrade path, also release a compatible version targeting OpenShift 4.8, which will allow you to publish an upgrade path using the skips and skipsRange configuration. If you do not push new versions compatible with 4.9 by September 30th, your package will be completely removed from OpenShift 4.9 until you have an updated version. ![]() Updating your Operator after OpenShift 4.9 is GA The OLM packaging format allows to specify with which OpenShift releases your operator is compatible and to which OpenShift versions it should be published.Īs a reminder, you can restrict which versions of your Operator target particular OpenShift versions. It is important that you publish an updated version of your operator to at least the OpenShift 4.8 catalog, so that users have a chance to upgrade before they upgrade their cluster to 4.9. For example, version 1.0.3 has been updated to use new APIs and replaces the previous version 1.0.2: Be sure to set the metadata to indicate that it works on both 4.8 and 4.9+. OpenShift 4.8 (Kubernetes 1.21) already understands the updated APIs so you may publish your updated Operator whenever you’d like. Uploading a new version of your Operator by September 30th is key to supporting a smooth upgrade path for your customers and preventing confusion. $ oc get Updating your Operator before OpenShift 4.9 is GA Information about the Users and Service Accounts using an API is available with this CLI command: Inside of an OpenShift cluster, you can also navigate to the Alerts section: bundle -select-optional suite =operatorframework -optional-values =k8s-version =1.22 If you developed your operator with the Operator-SDK you can also run a compatibility test suite on the operator metadata: The fastest check is to grep your codebase and metadata for all usage of “/v1beta1” and verify the above APIs aren’t being used. Checking for usage of Deprecated APIs in your product Keep in mind this change is not OpenShift-specific, the entire Kubernetes ecosystem is required to make this change and you may already be hearing about it from your customers. Customer clusters will be blocked from upgrading past OpenShift 4.8 if they are using your products and your Operators are using the retired APIs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |