Merge pull request #1722 from wallrj/remove-operatorhub

Announce the discontinuation of OperatorHub packages and remove the installation instructions

Author: wallrj

content/docs/installation/README.md

@@ -25,9 +25,6 @@ kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/
 
 📖 **helm**: You can [use helm to install cert-manager](./helm.md) and this also allows you to customize the installation if necessary.
 
-📖 **OperatorHub**: If you have an OpenShift cluster, consider [installing cert-manager via OperatorHub](./operator-lifecycle-manager.md),
-which you can do from the OpenShift web console.
-
 🚧 **cmctl**: Try the [experimental `cmctl x install` command](../reference/cmctl.md#install) to quickly install cert-manager.
 
 ## Continuous deployment

content/docs/installation/operator-lifecycle-manager.md

@@ -322,10 +322,6 @@
               "title": "b. Helm",
               "path": "/docs/installation/helm.md"
             },
-            {
-              "title": "c. OperatorHub (OLM)",
-              "path": "/docs/installation/operator-lifecycle-manager.md"
-            },
             {
               "title": "d. Continuous Deployment",
               "path": "/docs/installation/continuous-deployment-and-gitops.md"

content/docs/manifest.json

@@ -16,6 +16,18 @@ ACME issuer and Venafi Issuer.
 1. Venafi Issuer may fail to renew Certificates if the issuer has been configured for TPP with username-password authentication.
    For more details, refer to the [Venafi Issuer](#venafi-issuer) section below.
 
+### OperatorHub Packages Discontinued
+
+We no longer publish OperatorHub packages for cert-manager.
+Why? Because the cert-manager maintainers no longer have the time or resources to maintain and test those packages.
+cert-manager `v1.16.5` is the last release on OperatorHub.
+
+> ℹ️ [cert-manager `v1.16.5` for RedHat OpenShift OperatorHub](https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [cert-manager `v1.16.5` for `operatorhub.io`](https://github.com/k8s-operatorhub/community-operators/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [Archived `cert-manager-olm` repository](https://github.com/cert-manager/cert-manager-olm).
+
 ## Themes
 
 ### Helm

content/docs/releases/release-notes/release-notes-1.16.md

@@ -12,6 +12,18 @@ cert-manager v1.17 includes:
 
 ## Major Themes
 
+### OperatorHub Packages Discontinued
+
+We no longer publish OperatorHub packages for cert-manager.
+Why? Because the cert-manager maintainers no longer have the time or resources to maintain and test those packages.
+cert-manager `v1.16.5` is the last release on OperatorHub.
+
+> ℹ️ [cert-manager `v1.16.5` for RedHat OpenShift OperatorHub](https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [cert-manager `v1.16.5` for `operatorhub.io`](https://github.com/k8s-operatorhub/community-operators/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [Archived `cert-manager-olm` repository](https://github.com/cert-manager/cert-manager-olm).
+
 ### RSA Certificate Compliance
 
 The United States Department of Defense published a [memo: Department of Defense Transition to Stronger Public Key Infrastructure Algorithms](https://dl.dod.cyber.mil/wp-content/uploads/pki-pke/pdf/unclass-memo_dodcryptoalgorithms.pdf) in 2022 which introduced some requirements on the kinds of cryptography they require to be supported in software they use.

content/docs/releases/release-notes/release-notes-1.17.md

@@ -13,6 +13,18 @@ Be sure to review all new features and changes below, and read the full release
 
 ## Major Themes
 
+### OperatorHub Packages Discontinued
+
+We no longer publish OperatorHub packages for cert-manager.
+Why? Because the cert-manager maintainers no longer have the time or resources to maintain and test those packages.
+cert-manager `v1.16.5` is the last release on OperatorHub.
+
+> ℹ️ [cert-manager `v1.16.5` for RedHat OpenShift OperatorHub](https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [cert-manager `v1.16.5` for `operatorhub.io`](https://github.com/k8s-operatorhub/community-operators/tree/main/operators/cert-manager/1.16.5).
+>
+> ℹ️ [Archived `cert-manager-olm` repository](https://github.com/cert-manager/cert-manager-olm).
+
 ### ACME HTTP01 challenge paths now use `PathType` `Exact` in Ingress routes
 
 > ⚠️ Breaking change

content/docs/releases/release-notes/release-notes-1.18.md

@@ -40,9 +40,7 @@ and which is therefore available on
 [Community Operators Repository]: https://github.com/operator-framework/community-operators
 
 Please uninstall the existing cert-manager package and re-install
-by following the [OLM Installation Documentation][].
-
-[OLM Installation Documentation]: ../../installation/operator-lifecycle-manager.md
+by following the OLM Installation Documentation.
 
 ### Upgrading cert-manager CRDs and stored versions of cert-manager custom resources
 
@@ -376,4 +374,4 @@ After a lot of thinking, we have decided that trying to support every custom
 resource for every proxy could not be done in-tree due to the Go dependency
 weight that each integration adds. Jake Sanders proposed an [out-of-tree
 approach](https://github.com/cert-manager/cert-manager/issues/3924) that will be
-worked on as part of cert-manager 1.5.
+worked on as part of cert-manager 1.5.

content/docs/releases/release-notes/release-notes-1.4.md

@@ -22,10 +22,8 @@ and which is therefore available on
 [Community Operators Repository]: https://github.com/operator-framework/community-operators
 
 Please uninstall the existing cert-manager package and re-install
-by following the [OLM Installation Documentation][].
-
-[OLM Installation Documentation]: ../../installation/operator-lifecycle-manager.md
+by following the OLM Installation Documentation.
 
 ## Now Follow the Regular Upgrade Process
 
-From here on you can follow the [regular upgrade process](../../installation/upgrade.md).
+From here on you can follow the [regular upgrade process](../../installation/upgrade.md).

content/docs/releases/upgrading/upgrading-1.3-1.4.md

@@ -25,9 +25,6 @@ kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/
 
 📖 **helm**: You can [use helm to install cert-manager](./helm.md) and this also allows you to customize the installation if necessary.
 
-📖 **OperatorHub**: If you have an OpenShift cluster, consider [installing cert-manager via OperatorHub](./operator-lifecycle-manager.md),
-which you can do from the OpenShift web console.
-
 🚧 **cmctl**: Try the [experimental `cmctl x install` command](../reference/cmctl.md#install) to quickly install cert-manager.
 
 ## Continuous deployment