f3050740ef
Original names which gave errors: myServiceA, myServiceB Alatere suggestions: myServiceA --> myservicea, my_service_a, my-service-a myServiceB --> myserviceb, my_service_b, my-service-b
50 lines
2 KiB
Markdown
50 lines
2 KiB
Markdown
# Basic usage - host based routing
|
|
|
|
ingress-nginx can be used for many use cases, inside various cloud provider and supports a lot of configurations. In this section you can find a common usage scenario where a single load balancer powered by ingress-nginx will route traffic to 2 different HTTP backend services based on the host name.
|
|
|
|
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
|
|
kind: Ingress
|
|
metadata:
|
|
name: ingress-myservicea
|
|
annotations:
|
|
# use the shared ingress-nginx
|
|
kubernetes.io/ingress.class: "nginx"
|
|
spec:
|
|
rules:
|
|
- host: myservicea.foo.org
|
|
http:
|
|
paths:
|
|
- path: /
|
|
backend:
|
|
serviceName: myservicea
|
|
servicePort: 80
|
|
---
|
|
apiVersion: networking.k8s.io/v1beta1
|
|
kind: Ingress
|
|
metadata:
|
|
name: ingress-myserviceb
|
|
annotations:
|
|
# use the shared ingress-nginx
|
|
kubernetes.io/ingress.class: "nginx"
|
|
spec:
|
|
rules:
|
|
- host: myserviceb.foo.org
|
|
http:
|
|
paths:
|
|
- path: /
|
|
backend:
|
|
serviceName: myserviceb
|
|
servicePort: 80
|
|
```
|
|
|
|
When you apply this yaml, 2 ingress resources will be created managed by the **ingress-nginx** instance. Nginx is configured to automatically discover all ingress with the `kubernetes.io/ingress.class: "nginx"` annotation.
|
|
Please note that the ingress resource should be placed inside the same namespace of the backend resource.
|
|
|
|
On many cloud providers ingress-nginx will also create the corresponding Load Balancer resource. All you have to do is get the external IP and add a DNS `A record` inside your DNS provider that point myServiceA.foo.org and myServiceB.foo.org to the nginx external IP. Get the external IP by running:
|
|
|
|
```
|
|
kubectl get services -n ingress-nginx
|
|
```
|