Update cert-manager version (v1.9.1 -> v1.10.0)

Author: oscr

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.9.1"
+	CertManagerDefaultVersion = "v1.10.0"
 
 	// CertManagerDefaultURL defines the default cert-manager repository url to be used by clusterctl.
 	// NOTE: At runtime /latest will be replaced with the CertManagerDefaultVersion or with the

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

@@ -182,7 +182,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.9.1). See [clusterctl configuration](../configuration.md) for
+install a default version (currently cert-manager v1.10.0). See [clusterctl configuration](../configuration.md) for
 available options to customize this operation.
 
 <aside class="note warning">

docs/book/src/developer/guide.md

@@ -81,7 +81,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.9.1/cert-manager.yaml
+kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.10.0/cert-manager.yaml
 ```
 
 Ensure the cert-manager webhook service is ready before creating the Cluster API components.

docs/book/src/developer/providers/v1.2-to-v1.3.md

@@ -61,3 +61,4 @@ The default value is 0, meaning that the volume can be detached without any time
   * `ETCD_VERSION_UPGRADE_TO`
   * `COREDNS_VERSION_UPGRADE_TO`
   The variable `SkipUpgrade` could be set to revert to the old behaviour by making use of the `KUBERNETES_VERSION` variable and skipping the kubernetes upgrade.
+- cert-manager upgraded from v1.9.1 to v1.10.0.

docs/book/src/user/quick-start.md

@@ -531,7 +531,7 @@ The output of `clusterctl init` is similar to this:
 
 ```bash
 Fetching providers
-Installing cert-manager Version="v1.9.1"
+Installing cert-manager Version="v1.10.0"
 Waiting for cert-manager to be available...
 Installing Provider="cluster-api" Version="v1.0.0" TargetNamespace="capi-system"
 Installing Provider="bootstrap-kubeadm" Version="v1.0.0" TargetNamespace="capi-kubeadm-bootstrap-system"

docs/book/src/user/troubleshooting.md

@@ -161,7 +161,7 @@ clusterctl init --infrastructure docker
 ```
 ```bash
 Fetching providers
-Installing cert-manager Version="v1.9.1"
+Installing cert-manager Version="v1.10.0"
 Error: action failed after 10 attempts: failed to get cert-manager object /, Kind=, /: Object 'Kind' is missing in 'unstructured object has no kind'
 ```
 
@@ -173,7 +173,7 @@ cert-manager:
   url: "https://github.com/cert-manager/cert-manager/releases/latest/cert-manager.yaml"
 ```
 
-Alternatively a Cert Manager yaml file can be placed in the [clusterctl overrides layer](../clusterctl/configuration.md#overrides-layer) which is by default in `$HOME/.cluster-api/overrides`. A Cert Manager yaml file can be placed at `$(HOME)/.cluster-api/overrides/cert-manager/v1.9.1/cert-manager.yaml`
+Alternatively a Cert Manager yaml file can be placed in the [clusterctl overrides layer](../clusterctl/configuration.md#overrides-layer) which is by default in `$HOME/.cluster-api/overrides`. A Cert Manager yaml file can be placed at `$(HOME)/.cluster-api/overrides/cert-manager/v1.10.0/cert-manager.yaml`
 
 More information on the clusterctl config file can be found at [its page in the book](../clusterctl/configuration.md#clusterctl-configuration-file)
 

scripts/ci-e2e-lib.sh

@@ -200,9 +200,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.9.1"
-  kind::prepullImage "quay.io/jetstack/cert-manager-webhook:v1.9.1"
-  kind::prepullImage "quay.io/jetstack/cert-manager-controller:v1.9.1"
+  kind::prepullImage "quay.io/jetstack/cert-manager-cainjector:v1.10.0"
+  kind::prepullImage "quay.io/jetstack/cert-manager-webhook:v1.10.0"
+  kind::prepullImage "quay.io/jetstack/cert-manager-controller:v1.10.0"
 }
 
 # kind:prepullImage pre-pull a docker image if no already present locally.

test/e2e/config/docker.yaml

@@ -19,11 +19,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.9.1
+- name: quay.io/jetstack/cert-manager-cainjector:v1.10.0
   loadBehavior: tryLoad
-- name: quay.io/jetstack/cert-manager-webhook:v1.9.1
+- name: quay.io/jetstack/cert-manager-webhook:v1.10.0
   loadBehavior: tryLoad
-- name: quay.io/jetstack/cert-manager-controller:v1.9.1
+- name: quay.io/jetstack/cert-manager-controller:v1.10.0
   loadBehavior: tryLoad
 
 providers: