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

Updated v1beta1 to v1 as its deprecated (#7308)

Browse source
This commit is contained in:
Kundan Kumar 2021-07-05 02:38:19 +05:30 • committed by GitHub
parent 5acc0ab622
commit a21d28d01b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -5,7 +5,7 @@ ingress-nginx can be used for many use cases, inside various cloud provider and
First of all follow the instructions to install ingress-nginx. Then imagine that you need to expose 2 HTTP services already installed: `myServiceA`, `myServiceB`. Let's say that you want to expose the first at `myServiceA.foo.org` and the second at `myServiceB.foo.org`. One possible solution is to create two **ingress** resources:
```
apiVersion: networking.k8s.io/v1beta1
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-myservicea
@ -22,7 +22,7 @@ spec:
serviceName: myservicea
servicePort: 80
---
apiVersion: networking.k8s.io/v1beta1
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-myserviceb