From 51aa3d7f4e13eaa20d66fbd7d0c5c4797b4dfce9 Mon Sep 17 00:00:00 2001 From: Joe Heck Date: Mon, 26 Nov 2018 07:50:47 -0800 Subject: [PATCH] fix numbering of steps in quickstart Signed-off-by: Joe Heck --- docs/tutorials/quick-start/index.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/tutorials/quick-start/index.rst b/docs/tutorials/quick-start/index.rst index 54014d57d..ae3288bcf 100644 --- a/docs/tutorials/quick-start/index.rst +++ b/docs/tutorials/quick-start/index.rst @@ -215,7 +215,7 @@ control, for example as `example.your-domain.com`. This quickstart assumes you know how to assign a DNS entry to an IP address and will do so. -Step 2 - Deploy an Example Service +Step 4 - Deploy an Example Service ================================== Your service may have its own chart, or you may be deploying it directly with @@ -340,7 +340,7 @@ for our site. process of issuing a certificate uses that valdiation as proof that the request for the domain belongs to someone with sufficient control over the domain. -Step 3 - Deploy Cert Manager +Step 5 - Deploy Cert Manager ============================ We need to install cert-manager to do the work with kubernetes to request a @@ -414,7 +414,7 @@ are: .. _`CRD`: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ -Step 4 - Configure Let's Encrypt Issuer +Step 6 - Configure Let's Encrypt Issuer ======================================= We will set up two issuers for Let's Encrypt in this example. The Let's Encrypt @@ -497,7 +497,7 @@ Check on the status of the issuer after you create it: You should see the issuer listed with a registered account. -Step 5 - Deploy a TLS Ingress Resource +Step 7 - Deploy a TLS Ingress Resource ====================================== With all the pre-requisite configuration in place, we can now do the pieces