Merge pull request #11264 from k8s-infra-cherrypick-robot/cherry-pick-11263-to-release-1.8

[release-1.8] 🌱Bump cert manager to v1.16.0

Author: k8s-ci-robot

cmd/clusterctl/client/config/cert_manager_client.go

@@ -29,7 +29,7 @@ const (
 	CertManagerConfigKey = "cert-manager"
 
 	// CertManagerDefaultVersion defines the default cert-manager version to be used by clusterctl.
-	CertManagerDefaultVersion = "v1.15.3"
+	CertManagerDefaultVersion = "v1.16.0"
 
 	// CertManagerDefaultURL defines the default cert-manager repository url to be used by clusterctl.
 	// NOTE: At runtime CertManagerDefaultVersion may be replaced with the

docs/book/src/clusterctl/commands/init.md

@@ -194,7 +194,7 @@ If this happens, there are no guarantees about the proper functioning of `cluste
 Cluster API providers require a cert-manager version supporting the `cert-manager.io/v1` API to be installed in the cluster.
 
 While doing init, clusterctl checks if there is a version of cert-manager already installed. If not, clusterctl will
-install a default version (currently cert-manager v1.15.3). See [clusterctl configuration](../configuration.md) for
+install a default version (currently cert-manager v1.16.0). See [clusterctl configuration](../configuration.md) for
 available options to customize this operation.
 
 <aside class="note warning">

docs/book/src/developer/guide.md

@@ -83,7 +83,7 @@ The generated binary can be found at ./hack/tools/bin/envsubst
 You'll need to deploy [cert-manager] components on your [management cluster][mcluster], using `kubectl`
 
 ```bash
-kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.15.3/cert-manager.yaml
+kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.16.0/cert-manager.yaml
 ```
 
 Ensure the cert-manager webhook service is ready before creating the Cluster API components.

scripts/ci-e2e-lib.sh

@@ -270,9 +270,9 @@ EOL
 # the actual test run less sensible to the network speed.
 kind:prepullAdditionalImages () {
   # Pulling cert manager images so we can pre-load in kind nodes
-  kind::prepullImage "quay.io/jetstack/cert-manager-cainjector:v1.15.3"
-  kind::prepullImage "quay.io/jetstack/cert-manager-webhook:v1.15.3"
-  kind::prepullImage "quay.io/jetstack/cert-manager-controller:v1.15.3"
+  kind::prepullImage "quay.io/jetstack/cert-manager-cainjector:v1.16.0"
+  kind::prepullImage "quay.io/jetstack/cert-manager-webhook:v1.16.0"
+  kind::prepullImage "quay.io/jetstack/cert-manager-controller:v1.16.0"
 }
 
 # kind:prepullImage pre-pull a docker image if no already present locally.

test/e2e/config/docker.yaml

@@ -23,11 +23,11 @@ images:
   loadBehavior: tryLoad
 - name: gcr.io/k8s-staging-cluster-api/test-extension-{ARCH}:dev
   loadBehavior: tryLoad
-- name: quay.io/jetstack/cert-manager-cainjector:v1.15.3
+- name: quay.io/jetstack/cert-manager-cainjector:v1.16.0
   loadBehavior: tryLoad
-- name: quay.io/jetstack/cert-manager-webhook:v1.15.3
+- name: quay.io/jetstack/cert-manager-webhook:v1.16.0
   loadBehavior: tryLoad
-- name: quay.io/jetstack/cert-manager-controller:v1.15.3
+- name: quay.io/jetstack/cert-manager-controller:v1.16.0
   loadBehavior: tryLoad
 
 providers: