Certificate management
Learn about managing certificates that are created by the installer.
From foundational services version 4.6, IBM Certificate manager (cert-manager) is deprecated and its use is limited to IBM Cloud Pak® internal certificate management only. The recommended solution for using your certificates is Red Hat Cert Manager.
If you are using the Certificate manager operator service as part of an IBM Cloud Pak®, see the documentation for that IBM Cloud Pak® to learn more about how to install and use the operator service. For more information about IBM Cloud Paks, see IBM Cloud Paks that use IBM Cloud Pak foundational services.
What's new for the Certificate manager service
Installer version 4.6.x
- IBM Certificate manager (cert-manager) is deprecated: From foundational services version 4.6, IBM Certificate manager (cert-manager) is deprecated and its use is limited to IBM Cloud Pak® internal certificate management only. The recommended solution for using your certificates is Red Hat Cert Manager. For more information about how to migrate to Red Hat Cert Manager, see Migrating from IBM Certificate Manager to Red Hat Cert Manager.
Installer version 4.5.x
- Essential security updates.
Installer version 4.4.x
- Cert Manager operator is updated to support the
spec.labels
parameter in the custom resources of theCertManagerConfig
. You can set the labels to the Cert Manager operand resources such asDeployments
,StatefulSets
,Pods
,Secrets
,ConfigMaps
, andRoutes
.
Installer version 4.3.x
- The default size for
cert-manager-operator
is updated.
Installer version 4.1.x
- Certificate manager operator service is now synced with the open source cert-manager version (that is, foundational services cert-manager operands), to version 1.12.2.
Installer version 4.0.x
- You can now bring your own certificate (BYOC) in two ways:
- By using the
common-service
custom resource - By creating your own certificate manager resources
- By using the
How to check which service version you are using
You can check the installer version in the configmap by running the following command:
oc -n kube-public get ConfigMap ibmcloud-cluster-info -o jsonpath=’{.data.version}’
3.6.0
You can check the Common service operator full version and deployed namespace by running the following command:
oc get csv --all-namespaces | grep common-service-
common-service IBM Cloud Platform Common Services 3.6.3 ibm-common-service-operator.v3.5.6 Succeeded
ibm-common-services IBM Cloud Platform Common Services 3.6.3 ibm-common-service-operator.v3.5.6 Succeeded