Everything you want to know about Ingress

Janakiram MSVAnalyst | Advisor | ArchitectJanakiram & AssociatesGoogle Developer Expert

@janakiramm

Joseph JacksEntrepreneur in ResidenceQuantumFounder, KubeCon

@asynchio

Objectives

● Recap of Services in Kubernetes● What is Ingress?● Services vs Ingress● Use Cases for Ingress

Kubernetes Cluster

Understanding Services

Node 1 Node 2 Node 3

S1 S2 S3 S4

Recap - Service Types

● ClusterIP○ Service is reachable only from inside of the cluster.

● NodePort○ Service is reachable through <NodeIP>:NodePort address.

● LoadBalancer○ Service is reachable through an external load balancer mapped to

<NodeIP>:NodePort address

Exposing Pods

Kubernetes Cluster

Node 1 Node 2 Node 3

S1 S2 S3 S4

Internet

Overview of Ingress

● An Ingress is a collection of rules that allow inbound connections to reach the cluster services

● Configured to expose services through○ External URLs○ Load Balancers○ SSL-terminated endpoints○ Name-based virtual hosting

Exposing Services through Ingress

Node 1 Node 2 Node 3

Internet

DemoExploring Ingress with GKE

Ingress in Kubernetes

● Special type of controller deployed within the cluster● A daemon, deployed as a Kubernetes Pod, that watches

the apiserver's /ingresses endpoint for updates to the Ingress resource

● Fundamentally different from other controllers

Upcoming WebinarBuilding CI/CD Pipelines with Jenkins and Kubernetes9AM PST, Wednesday, Aug 16th

Attend this webinar to learn how to configure CI/CD pipelines with Jenkins and Kubernetes. We will show you to how to automate deployments from source code to production clusters.

Register at kube.live for the upcoming webinars

● Integration with Jenkins● Kubernetes Plugin● Performing rolling upgrades

Thank You!Send your Feedback / Questions / Comments jani@janakiram.com