DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fixed markdown typo

Browse source 
Signed-off-by: Mathis Van Eetvelde <mathis.vaneetvelde@protonmail.com>
This commit is contained in:
Mathis Van Eetvelde 2021-05-06 23:02:40 +02:00
parent 8dcf172f88
commit 727020b3ac
No known key found for this signature in database
GPG key ID: 89A5CF6F5F2F93C4
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/deploy/index.md
View file

@ -15,16 +15,16 @@
!!! attention !!! attention
The first time the ingress controller starts, two [Jobs](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) create the SSL Certificate used by the admission webhook. The first time the ingress controller starts, two [Jobs](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) create the SSL Certificate used by the admission webhook.
For this reason, there is an initial delay of up to two minutes until it is possible to create and validate Ingress definitions. For this reason, there is an initial delay of up to two minutes until it is possible to create and validate Ingress definitions.
You can wait until it is ready to run the next command: You can wait until it is ready to run the next command:
```yaml ```yaml
kubectl wait --namespace ingress-nginx \ kubectl wait --namespace ingress-nginx \
--for=condition=ready pod \ --for=condition=ready pod \
--selector=app.kubernetes.io/component=controller \ --selector=app.kubernetes.io/component=controller \
--timeout=120s --timeout=120s
``` ```
## Contents ## Contents