From 7fa88f691a17620113d39b72b87c3d91c452c862 Mon Sep 17 00:00:00 2001 From: George Wilson Date: Tue, 22 Sep 2020 09:37:52 +0100 Subject: [PATCH] Update version. Remove CRD Flag --- .../v2.x/en/installation/k8s-install/helm-rancher/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 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 3d1e76fc86a..8ea026ca56f 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,6 +88,9 @@ 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/v1.0.1/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 @@ -111,8 +114,7 @@ helm repo update helm install \ cert-manager jetstack/cert-manager \ --namespace cert-manager \ - --version v0.15.0 \ - --set installCRDs=true + --version v1.0.1 ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: