- Issued:
- 2024-01-16
- Updated:
- 2024-01-16
RHEA-2024:0260 - Product Enhancement Advisory
Synopsis
[OpenShift v4.13-v4.14] cert-manager Operator for Red Hat OpenShift 1.13.0
Type/Severity
Product Enhancement Advisory
Topic
[OpenShift v4.13-v4.14] cert-manager Operator for Red Hat OpenShift 1.13.0
Description
The cert-manager Operator for Red Hat OpenShift builds on top of Kubernetes, introducing certificate authorities
and certificates as first-class resource types in the Kubernetes API. This makes it possible to provide
certificates-as-a-service to developers working within your Kubernetes cluster.
Solution
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
For details on how to apply this update, refer to:
Affected Products
- Cert Manager support for Red Hat OpenShift release 1.13 x86_64
- Cert Manager support for Red Hat OpenShift release for Power 1.13 ppc64le
- Cert Manager support for Red Hat OpenShift release for IBM Z 1.13 s390x
- Cert Manager support for Red Hat OpenShift release ARM 64 1.13 aarch64
Fixes
- CM-189 - Bump cert-manager to v1.13
- CM-194 - Create branch on midstream (gitlab/cpaas-midstream-cfe/openshift-cert-manager)
- CM-190 - Rebase operator to v1.13.x version (github/openshift/cert-manager-operator)
- CM-201 - Add power/z architectures as labels in the CSV
- CM-208 - Add arm64 architecture as supported label in the CSV
- CM-215 - [cert-manager-1.13] Cert-manager-operator pod has incorrect nodeaffinitiy config
- CM-236 - Bump operator to use upstream cert-manager 1.13.2
- CM-183 - As a developer, I would require feature annotations in bundle for CVP tests to pass
- OCPBUGS-8665 - cert-manager does not work with "Managed Identity Using AAD Pod Identities"
- CM-144 - As a developer, I would like to test the workflow of changing default ingress in AWS, GCP, Azure with cert-manager certificates
- CM-145 - As a tester, I would like to test the workflow of changing default ingress in bare-metal, vSphere with cert-manager certificates
- CM-146 - As a tester, I would like to test renewal of certificates when cert-manager issued certificate is used with default ingresscontroller
- CM-148 - As a developer, I would like to test the workflow of adding a new cert-manager certificate with API server for day-2, in case of AWS, GCP, Azure
- CM-149 - As a tester, I would like to test the workflow of adding a new cert-manager certificate with API server for day-2, in case of bare-metal, vSphere
- CM-150 - As a tester, I would like to test upgrades from OCP vN-1 -> vN for a cluster which has both Ingress, API server configured with cert-manager certificates
- CM-151 - As a tester, verify if http01 solver is affected when changing the default ingresscontroller certificate
- CM-152 - As a developer, I would like to verify if default IngressController can be used with self-signed, CA-issued certificates and document it?s pitfalls if any
- CM-153 - As a developer, I would like to verify if adding serving cert for self-signed, CA-issued certificates can be used and document pitfalls if any
- CM-154 - As a developer, I would like to list steps and verify the behaviour of using the new API server endpoint from a non-default ingresscontroller and customize the domain/host
- CM-228 - As a tester, first get familiar with and practice OCP feature managing API Server certificate before involving cert-manager
- CM-229 - As a tester, first get familiar with and practice the OCP feature managing Ingress default certificate before involving cert-manager
- CM-252 - Bump operator to use upstream cert-manager 1.13.3
- CM-139 - Managing certs on day-2 for API Server and Ingress with cert-manager Operator for RedHat OpenShift
- CM-140 - Cert-manager builds for Non-x86 systems
CVEs
References
(none)
aarch64
cert-manager/cert-manager-operator-bundle@sha256:b74dbf8e6b71f58edf7b6e9279d637441756f094cf99e0aef20896d61303e6f6 |
cert-manager/cert-manager-operator-rhel9@sha256:b391aa9f50f39230deab67886986203f225ed95441ce350b86df4064daac922d |
cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:8dcfe345a2152921ef620f18a863fcc7ad611220d5e73a4871a784cdd2af7506 |
cert-manager/jetstack-cert-manager-rhel9@sha256:7ce61e350f3cebdb6eb05e142b69160e2215f6bafd98ae1e9ad72071458057c6 |
ppc64le
cert-manager/cert-manager-operator-bundle@sha256:cfd0cee083649b32cbb671b54faabeb416eeaee419a319102e73dc91a2da5189 |
cert-manager/cert-manager-operator-rhel9@sha256:ad33953d676e05b515fd56739fc7a621a328304e049d552773c34f7c617e41a7 |
cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:ed4559cf55ac19596ab0d0b13e498f56f8287c3d337f04ad88b7d1b4e9576f8f |
cert-manager/jetstack-cert-manager-rhel9@sha256:b0be9b2f869c1eb7548a1c376e04a9921e52b5dae9256a7e464d8920eb562a2a |
s390x
cert-manager/cert-manager-operator-bundle@sha256:dcdbdaa472c99bd59018b8c1129b6576f71f1e7d2b50d5028f31b9288cc05b2f |
cert-manager/cert-manager-operator-rhel9@sha256:bb69592d11aeac0d760acb1cf8f0575f128952bfcb4be17e800cf6b75979c241 |
cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:0d8a393ecf6bf36e2b09e5705b72611896819b92f3d55b1657f100242c313f07 |
cert-manager/jetstack-cert-manager-rhel9@sha256:5e4fa60d3c73903911d16c180816d1c1a1a09c1ceb3c395f12137572e05abeff |
x86_64
cert-manager/cert-manager-operator-bundle@sha256:e07e1e7079f57e91a362d9151804577cfec8a41bb8b63872764f80514f5ebaaa |
cert-manager/cert-manager-operator-rhel9@sha256:534c753a923929f94d18617b3520bda0d1dad994128fe68213f893059535349a |
cert-manager/jetstack-cert-manager-acmesolver-rhel9@sha256:18f84597c57b222c815179803362c3e45567c565512c9c1d6efd4c578396c02f |
cert-manager/jetstack-cert-manager-rhel9@sha256:93bedad1dbccfab58b7f86da879c32b782a59f75799f434b08670bff76ee1803 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.