> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Solution Ingress Networking 1 > This article covers configuring and updating an Ingress Controller to manage traffic across multiple applications and namespaces in a Kubernetes environment. In this lab, we will walk through configuring an Ingress Controller, examining deployed resources, and updating Ingress paths to route traffic appropriately across multiple applications and namespaces. *** ## Environment Overview Begin by reviewing your cluster environment. Verify the nodes, namespaces, deployments, and pods. In this setup, there is one node with various namespaces hosting different components. For instance, run the following command to list all pods across all namespaces: ```bash theme={null} root@controlplane ~ ➜ k get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE app-space default-backend-7f8f4c484-zw8kb 1/1 Running 0 103s app-space webapp-video-d54b764b6-d5rnd 1/1 Running 0 104s app-space webapp-wear-5b84c4f565-djh5m 1/1 Running 0 101s ingress-nginx ingress-nginx-admission-create-wbssr 0/1 Completed 0 101s ingress-nginx ingress-nginx-admission-patch-2pmxg 0/1 Completed 0 101s kube-system corends-648979b5d-mwkh8 1/1 Running 0 11m kube-system etcd-controlplane 1/1 Running 0 12m kube-system kube-apiserver-controlplane 1/1 Running 0 12m kube-system kube-controller-manager-controlplane 1/1 Running 0 12m kube-system kube-flannel-ds-xtsxv 1/1 Running 0 11m kube-system kube-proxy-m26kb 1/1 Running 0 11m kube-system kube-scheduler-controlplane 1/1 Running 0 12m root@controlplane ~ ➜ ``` From the output, you can see pods running in several namespaces (such as *app-space*, *ingress-nginx*, and *kube-system*). The Ingress Controller is specifically deployed in the **ingress-nginx** namespace. *** ## Ingress Controller Details To verify the Ingress Controller deployment, execute the command below: ```bash theme={null} root@controlplane ~ ⟩ k get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE app-space default-backend-7f8f4c484-zw8kb 1/1 Running 0 103s app-space webapp-video-d54b764b6-d5rn5 1/1 Running 0 104s app-space webapp-wear-5b44cf565-5hjmj 1/1 Running 0 101s ingress-nginx ingress-nginx-admission-create-wbssr 0/1 Completed 0 101s ingress-nginx ingress-nginx-admission-patch-2pmxg 0/1 Completed 0 101s ingress-nginx ingress-nginx-controller-546d8cf744-4hz72 1/1 Running 0 101s kube-system coredns-64897985d-mwkh8 1/1 Running 0 11m kube-system etcd-controlplane 1/1 Running 0 12m kube-system kube-apiserver-controlplane 1/1 Running 0 12m kube-system kube-controller-manager-controlplane 1/1 Running 0 12m kube-system kube-flannel-ds-xtsxv 1/1 Running 0 11m kube-system kube-proxy-m26kb 1/1 Running 0 11m kube-system kube-scheduler-controlplane 1/1 Running 0 12m root@controlplane ~ ⟩ ``` Notice that the Ingress Controller resource is named `ingress-nginx-controller` and operates within the **ingress-nginx** namespace. *** ## Application and Ingress Resource Applications are deployed within the **app-space** namespace. In our scenario, three application pods are running: * A default backend * A web application for video streaming * A web application for wear services To view the Ingress resource, run: ```bash theme={null} k get ingress -A ``` The output will display an Ingress resource from the **app-space** namespace: ```bash theme={null} NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE app-space ingress-wear-watch * 10.96.152.118 80 3m1s ``` To gather more details, describe the Ingress resource: ```bash theme={null} k describe ingress ingress-wear-watch -n app-space ``` The description reveals: * Two paths:\ • `/wear` routes to `wear-service` on port 8080.\ • `/watch` routes to `video-service` on port 8080. * A default backend (`default-http-backend`) is configured to handle unmatched requests. * The host is set to `*`, meaning the rules apply across all hosts. A request made to the Ingress without a matching path results in a 404 error as the default backend is invoked. For example: * Accessing `.../wear` opens the wear application. * Accessing `.../watch` (which will later be changed to `.../stream`) serves the video streaming application. *** ## Updating the Ingress Resource ### Redirecting Video Streaming to "/stream" To expose the video streaming application under the new URL path `/stream`: 1. Edit the Ingress resource for the **app-space** namespace. 2. Change the path from `/watch` to `/stream`. Below is the updated Ingress YAML specification: ```yaml theme={null} apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-wear-watch namespace: app-space annotations: nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - http: paths: - path: /wear pathType: Prefix backend: service: name: wear-service port: number: 8080 - path: /stream pathType: Prefix backend: service: name: video-service port: number: 8080 status: loadBalancer: ingress: - ip: 10.96.152.118 ``` After applying these modifications: * Navigating to `/watch` now results in a 404 error. * Accessing `/stream` correctly displays the video streaming application. After updating the Ingress resource, always verify the configuration using: * `k get ingress -A` * `k describe ingress ingress-wear-watch -n app-space` This ensures the new path registrations are active. *** ## Adding a Path for the Food Delivery Application The business has expanded by incorporating a food delivery service, now deployed in the **app-space** namespace. First, verify the deployments: ```bash theme={null} k get deploy -n app-space ``` Example output: ```bash theme={null} NAME READY UP-TO-DATE AVAILABLE AGE default-backend 1/1 1 1 7m53s webapp-food 1/1 1 1 20s webapp-video 1/1 1 1 7m54s webapp-wear 1/1 1 1 7m54s ``` Then, check the services: ```bash theme={null} k get svc -n app-space ``` Example output: ```bash theme={null} NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default-http-backend ClusterIP 10.102.190.18 80/TCP 8m22s food-service ClusterIP 10.108.9.190 8080/TCP 49s video-service ClusterIP 10.107.118.120 8080/TCP 8m22s wear-service ClusterIP 10.110.195.79 8080/TCP 8m23s ``` To expose the food delivery application, update the Ingress in the **app-space** namespace by adding an `/eat` path. For example: ```yaml theme={null} apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-wear-watch namespace: app-space annotations: nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - http: paths: - path: /wear pathType: Prefix backend: service: name: wear-service port: number: 8080 - path: /stream pathType: Prefix backend: service: name: video-service port: number: 8080 - path: /eat pathType: Prefix backend: service: name: food-service port: number: 8080 status: loadBalancer: ingress: - ip: 10.96.152.118 ``` Once applied: * Accessing `.../eat` displays the food delivery application. * All paths will be correctly routed to their respective services. *** ## Integrating a New Payment Service in a Separate Namespace A new critical payment service is deployed in its own namespace, **critical-space**. To verify the payment pods, run: ```bash theme={null} k get pods -A ``` A sample output should include: ```bash theme={null} NAMESPACE NAME READY STATUS RESTARTS AGE app-space webapp-food-... 1/1 Running 0 ... critical-space webapp-pay-67888454d4b-wl8ks 1/1 Running 0 13s ``` Now, check the payment deployment: ```bash theme={null} k get deploy -n critical-space ``` Example output: ```bash theme={null} NAME READY UP-TO-DATE AVAILABLE AGE webapp-pay 1/1 1 1 22s ``` Then, inspect the payment service details: ```bash theme={null} k get svc -n critical-space ``` Example output: ```bash theme={null} NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE pay-service ClusterIP 10.107.31.180 8282/TCP 119s ``` Following best practices, each namespace should manage its own Ingress. Create a new Ingress resource in **critical-space** to expose the payment service at the `/pay` path. Use the imperative command: ```bash theme={null} kubectl create ingress ingress-pay -n critical-space --rule="/pay=pay-service:8282" ``` Verify the new Ingress: ```bash theme={null} k get ingress -n critical-space ``` Expected output: ```bash theme={null} NAME CLASS HOSTS ADDRESS PORTS AGE ingress-pay * 80 10s ``` Describing the Ingress provides further details: ```bash theme={null} k describe ingress ingress-pay -n critical-space ``` Output shows: * The rule routes `/pay` to `pay-service` on port 8282. * A default backend is present. By default, the Ingress does not modify the URL path. If the payment application expects requests at `/` rather than `/pay`, add a rewrite annotation. To add the path rewrite, update the payment Ingress with the following YAML: ```yaml theme={null} apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-pay namespace: critical-space annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - http: paths: - path: /pay pathType: Exact backend: service: name: pay-service port: number: 8282 status: loadBalancer: ingress: - ip: 10.96.152.118 ``` After applying this change, requests to `/pay` will be rewritten to `/` before reaching the payment service, ensuring proper application functionality. *** ## Conclusion This lab demonstrated how to configure and update an Ingress Controller across multiple namespaces and applications. We: * Examined the cluster environment. * Verified and detailed the Ingress Controller deployment. * Updated the Ingress resource to change a URL path. * Added a new path for a food delivery application. * Created a separate Ingress for a critical payment service with proper path rewrite. Each modification was verified by inspecting the Ingress resources and testing the endpoints to ensure a smooth transition.