From 7e00b42c1a357f5fad80000579475c95ad260c7a Mon Sep 17 00:00:00 2001 From: Jeff Grafton Date: Fri, 8 Feb 2019 11:30:25 -0800 Subject: [PATCH] docs: no need to apply 00-crds.yaml when installing with regular manifests Signed-off-by: Jeff Grafton --- docs/getting-started/install.rst | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/docs/getting-started/install.rst b/docs/getting-started/install.rst index cd7b5b162..5a610f88a 100644 --- a/docs/getting-started/install.rst +++ b/docs/getting-started/install.rst @@ -50,16 +50,13 @@ cert-manager runs in: You can read more about the webhook on the :doc:`webhook document <./webhook>`. -We can now go ahead and install cert-manager. This is a two-stage process where -we first install the CustomResourceDefinition resources, and then afterwards -install cert-manager along with the webhook component: +We can now go ahead and install cert-manager. All resources +(the CustomResourceDefinitions, cert-manager, and the webhook component) +are included in a single YAML manifest file: .. code-block:: shell - # Install the CustomResourceDefinition resources - kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.6/deploy/manifests/00-crds.yaml - - # Install cert-manager itself + # Install the CustomResourceDefinitions and cert-manager itself kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.6/deploy/manifests/cert-manager.yaml .. note:: @@ -75,7 +72,7 @@ install cert-manager along with the webhook component: 'permission denied' error when creating some of these resources. This is a nuance of the way GKE handles RBAC and IAM permissions, and as such you should 'elevate' your own privileges to that of a 'cluster-admin' **before** - running the above commands. If you have already run the above commands, you + running the above command. If you have already run the above command, you should run them again after elevating your permissions:: kubectl create clusterrolebinding cluster-admin-binding \