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

checking mkdocs & ghpages (#8150)

Browse source
This commit is contained in:
Long Wu Yuan 2022-01-17 05:35:28 +05:30 committed by GitHub
parent 3732681588
commit 784f9c53bb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/user-guide/basic-usage.md
View file

@ -6,7 +6,7 @@ First of all follow the instructions to install ingress-nginx. Then imagine that
Let's say that you want to expose the first at `myServiceA.foo.org` and the second at `myServiceB.foo.org`.
If cluster version < 1.19 you can create two **ingress** resources like this:
If the cluster version is < 1.19, you can create two **ingress** resources like this:
```
apiVersion: networking.k8s.io/v1beta1
@ -91,4 +91,4 @@ On many cloud providers ingress-nginx will also create the corresponding Load Ba
kubectl get services -n ingress-nginx
```
To test inside minikube refer to this documentation: [Set up Ingress on Minikube with the NGINX Ingress Controller](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/)
To test inside minikube refer to this documentation: [Set up Ingress on Minikube with the NGINX Ingress Controller](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/)