kubernetes-training

• Ingress helps to access application using external configured URL -> route traffics to different services with SSL functionalities.
• Is layer 7’s load balancer that can be configured using K8s’s primitives
• Ingress needs to be exposed to be visible outside the cluster : either published it as a nodeport or via cloud provider. This is a one-time configuration. All of the configuration later on for services will use Ingress-Controller

Ingress in Kubernetes cluster

1. Deploy any solution: HAProxy, Nginx, Traefik -> ingress-controller
2. Specify a set of rule to configure the ingress ->ingress-resources
   1. Ingress resources are created using definition files

INGRESS CONTROLLER

• This lectures mention about NGINX specifically
  1. Deployment
  2. ConfigMap:
  1. decouple setting for error, keep-alive, and ssl option
  2. could be blank initially, will modify later
     1. .spec.env : NGINX service requires these to read the config data from within the pod
  3. POD_NAME
  4. NAME_SPACE

1. Specifiy ports used by the controller

2. Service for the ingress controller

3. Service Account with Roles, ClusterRoles and RoleBinding for Authentication

INGRESS RESOURCES

1. Same host, different path
   • Errata for apiversion,servicename, and serviceport
2. Different host

   Rewrite target

   • Article

     [!Note] This link is specific for NGINX