Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RH 4.10 and 4.11 Certification #938

Closed
udnay opened this issue Nov 14, 2022 · 1 comment · Fixed by #964
Closed

RH 4.10 and 4.11 Certification #938

udnay opened this issue Nov 14, 2022 · 1 comment · Fixed by #964

Comments

@udnay
Copy link
Collaborator

udnay commented Nov 14, 2022

The OpenShift Operator certification is the foundation of our Partner Alliance with Red Hat. Maintaining the certification on current versions is a qualification to continue to be a Red Hat Strategic Partner.

The certified operator which is available on OpenShift’s OperatorHub has always been the most seamless way to deploy CockroachDB on OpenShift. We need to continue to maintain our certification with the latest versions of OpenShift so prospective users/customers continue to have the deployment option available on newer releases of OpenShift.

Certification of the operator is a self service process on Red Hat’s partner portal. Steps for getting the Operator certified (https://redhat-connect.gitbook.io/partner-guide-for-red-hat-openshift-and-container/):

certified_operator

The CockroachDB K8s operator is currently certified up to OpenShift v4.9 which was GA on October 18, 2021 and its maintenance support ends on April 18, 2023. Prospective users/customers will care about our certification on OpenShift v4.10 and onwards due to the Red Hat OpenShift Container Platform Life Cycle Policy (https://access.redhat.com/support/policy/updates/openshift)

@udnay
Copy link
Collaborator Author

udnay commented Nov 14, 2022

A draft PR of the work can be seen #916. The release process was updated and required an exemption to allow our container to run in a privileged mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant