In this example we use the VirtualServer and VirtualServerRoute resources to configure load balancing for the modified cafe application from the Basic Configuration example. We have put the load balancing configuration as well as the deployments and services into multiple namespaces. Instead of one namespace, we now use three: tea, coffee, and cafe.

• In the tea namespace, we create the tea deployment, service, and the corresponding load-balancing configuration.
• In the coffee namespace, we create the coffee deployment, service, and the corresponding load-balancing configuration.
• In the cafe namespace, we create the cafe secret with the TLS certificate and key and the load-balancing configuration for the cafe application. That configuration references the coffee and tea configurations.

1. Follow the installation instructions to deploy the Ingress Controller with custom resources enabled.

2. Save the public IP address of the Ingress Controller into a shell variable:

   IC_IP=XXX.YYY.ZZZ.III

3. Save the HTTPS port of the Ingress Controller into a shell variable:

   IC_HTTPS_PORT=<port number>

Create the required tea, coffee, and cafe namespaces:

kubectl create -f namespaces.yaml

1. Create the tea deployment and service in the tea namespace:

   kubectl create -f tea.yaml

2. Create the coffee deployment and service in the coffee namespace:

   kubectl create -f coffee.yaml

1. Create the VirtualServerRoute resource for tea in the tea namespace:

   kubectl create -f tea-virtual-server-route.yaml

2. Create the VirtualServerRoute resource for coffee in the coffee namespace:

   kubectl create -f coffee-virtual-server-route.yaml

3. Create the secret with the TLS certificate and key in the cafe namespace:

   kubectl create -f cafe-secret.yaml

4. Create the VirtualServer resource for the cafe app in the cafe namespace:

   kubectl create -f cafe-virtual-server.yaml

1. Check that the configuration has been successfully applied by inspecting the events of the VirtualServerRoutes and VirtualServer:

   kubectl describe virtualserverroute tea -n tea

   . . .
   Events:
     Type     Reason                 Age   From                      Message
     ----     ------                 ----  ----                      -------
     Warning  NoVirtualServersFound  2m    nginx-ingress-controller  No VirtualServer references VirtualServerRoute tea/tea
     Normal   AddedOrUpdated         1m    nginx-ingress-controller  Configuration for tea/tea was added or updated
   

   kubectl describe virtualserverroute coffee -n coffee

   . . .
   Events:
     Type     Reason                 Age   From                      Message
     ----     ------                 ----  ----                      -------
     Warning  NoVirtualServersFound  2m    nginx-ingress-controller  No VirtualServer references VirtualServerRoute coffee/coffee
     Normal   AddedOrUpdated         1m    nginx-ingress-controller  Configuration for coffee/coffee was added or updated
   

   kubectl describe virtualserver cafe -n cafe

   . . .
   Events:
     Type    Reason          Age   From                      Message
     ----    ------          ----  ----                      -------
     Normal  AddedOrUpdated  1m    nginx-ingress-controller  Configuration for cafe/cafe was added or updated
   

2. Access the application using curl. We'll use curl's --insecure option to turn off certificate verification of our self-signed certificate and --resolve option to set the IP address and HTTPS port of the Ingress Controller to the domain name of the cafe application:

   To get coffee:

   curl --resolve cafe.example.com:$IC_HTTPS_PORT:$IC_IP https://cafe.example.com:$IC_HTTPS_PORT/coffee --insecure

   Server address: 10.16.1.193:80
   Server name: coffee-7dbb5795f6-mltpf
   ...
   

   If your prefer tea:

   curl --resolve cafe.example.com:$IC_HTTPS_PORT:$IC_IP https://cafe.example.com:$IC_HTTPS_PORT/tea --insecure

   Server address: 10.16.0.157:80
   Server name: tea-7d57856c44-674b8
   ...