From 28e18f914c8cb6ddc954b499045b6d63605213ae Mon Sep 17 00:00:00 2001 From: George Wilson Date: Tue, 30 Jun 2020 19:50:25 +0100 Subject: [PATCH] Use the installCRDs option for cert-manager --- .../v2.x/en/installation/k8s-install/helm-rancher/_index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md b/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md index 74aa80b7789..3d1e76fc86a 100644 --- a/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md +++ b/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md @@ -88,9 +88,6 @@ This step is only required to use certificates issued by Rancher's generated CA These instructions are adapted from the [official cert-manager documentation](https://cert-manager.io/docs/installation/kubernetes/#installing-with-helm). ``` -# Install the CustomResourceDefinition resources separately -kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v0.15.0/cert-manager.crds.yaml - # **Important:** # If you are running Kubernetes v1.15 or below, you # will need to add the `--validate=false` flag to your @@ -114,7 +111,8 @@ helm repo update helm install \ cert-manager jetstack/cert-manager \ --namespace cert-manager \ - --version v0.15.0 + --version v0.15.0 \ + --set installCRDs=true ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: