{"id":36731,"date":"2022-12-22T16:30:09","date_gmt":"2022-12-22T11:00:09","guid":{"rendered":"http:\/\/ismiletechnologies.com\/?p=36731"},"modified":"2022-12-23T04:35:13","modified_gmt":"2022-12-22T23:05:13","slug":"understanding-the-differences-between-kubernetes-ingress-and-load-balancer","status":"publish","type":"post","link":"https:\/\/ismiletechnologies.com\/en_us\/devops\/understanding-the-differences-between-kubernetes-ingress-and-load-balancer\/","title":{"rendered":"Understanding the Differences Between Kubernetes Ingress and Load Balancer"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In Kubernetes, service types determine how users or external traffic can access Services, which define a group of Pods and how to access them. There are three major types:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t
  1. Load Balancer\u00a0\u00a0<\/li>
  2. Cluster IP\u00a0\u00a0<\/li>
  3. Node Port<\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t
    \n\t\t\t\n\t\t\t\t\t\t<\/span>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t

    Kubernetes Ingress: <\/h2>\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    The Kubernetes Ingress handles external access to the services; it is not a Service, like the other options, but rather an API object. This works differently than Services because it creates an Ingress resource that routes traffic based on rules. It sets up an external load balancer that connects to the Ingress and then routes traffic to the service, following the rules. With this, admins can route multiple back-end services via one IP address.\u00a0\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t

    Load balancer: <\/h2>\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    A load balancer spreads out workloads evenly across servers or, in this case, Kubernetes clusters. In addition to connecting users with a Service, if a server fails, the workload is directed to a backup server, which reduces the effect on users. Load balancers sit between servers and the internet. They direct user requests to available servers. If demand is high, they can add servers; if demand is low, they can drop servers. However, each service requires its load balancer.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t

    NodePort vs. ClusterIP:<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Another Kubernetes networking option is to set the service type as NodePort. With NodePort, you can set up your load balancers to configure environments Kubernetes doesn’t fully support or expose the IP address of one or more nodes. This opens a way for external traffic to reach the nodes.\u00a0\u00a0\u00a0\u00a0\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t