Sign in Subscribe
devops

Path Based - Simple Fanout Ingress on Kubernetes

Bala Subramani K

• 4 min read
Path Based - Simple Fanout Ingress on Kubernetes

Part -I

Ingress on Kubernetes Cluster
On Local Cluster Created by using Kubeadm Why Ingress need on Kubernetes? Ingress is a key component in Kubernetes that provides HTTP and HTTPS routing to services based on rules defined by the user. Ingress may provide load balancing, SSL termination and name-based virtual hosting. In this blog, am going
Kubelancer NewsletterBala Subramani K

Part -II

Host Based Ingress on Kubernetes Cluster
Part -I Ingress on Kubernetes ClusterOn Local Cluster Created by using Kubeadm Why Ingress need on Kubernetes? Ingress is a key component in Kubernetes that provides HTTP and HTTPS routing to services based on rules defined by the user. Ingress may provide load balancing, SSL termination and name-based virtual hosting.
Kubelancer NewsletterBala Subramani K

Let continue with Part - III ...

Simple fanout / Path Based Ingress - Demo

Expose multiple services by using single IP address.

Create three deployment and services.

vi simplesite-deployment-services.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: home-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: home
  template:
    metadata:
      labels:
        app: home
    spec:
      containers:
        - name: home-container
          image: kubelancer/simplehome:v1.0.0
          ports:
            - containerPort: 8080
          env:                  
            - name: HOME_SERVICE_URL
              value: "http://home-service:8080"
            - name: BLOG_SERVICE_URL
              value: "http://blog-service:8081"
            - name: SERVICES_SERVICE_URL
              value: "http://services-service:8082"

---
apiVersion: v1
kind: Service
metadata:
  name: home-service
spec:
  selector:
    app: home
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080
  type: ClusterIP

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: blog-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: blog
  template:
    metadata:
      labels:
        app: blog
    spec:
      containers:
        - name: blog-container
          image: kubelancer/simpleblog:v1.0.0
          ports:
            - containerPort: 8081
          env:
            - name: HOME_SERVICE_URL
              value: "http://home-service:8080"
            - name: BLOG_SERVICE_URL
              value: "http://blog-service:8081"
            - name: SERVICES_SERVICE_URL
              value: "http://services-service:8082"

---
apiVersion: v1
kind: Service
metadata:
  name: blog-service
spec:
  selector:
    app: blog
  ports:
    - protocol: TCP
      port: 8081
      targetPort: 8081
  type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: services-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: services
  template:
    metadata:
      labels:
        app: services
    spec:
      containers:
        - name: services-container
          image: kubelancer/simpleservices:v1.0.0
          ports:
            - containerPort: 8082
          env:
            - name: HOME_SERVICE_URL
              value: "http://home-service:8080"
            - name: BLOG_SERVICE_URL
              value: "http://blog-service:8081"
            - name: SERVICES_SERVICE_URL
              value: "http://services-service:8082"
---
apiVersion: v1
kind: Service
metadata:
  name: services-service
spec:
  selector:
    app: services
  ports:
    - protocol: TCP
      port: 8082
      targetPort: 8082
  type: ClusterIP
  • Apply the deployment and services
kubectl apply -f simplesite-deployment-services.yaml
  • List deployment,pods,svc
kubectl get deployment,pod,svc -o wide

Output

Create ingress (path-based)

vi ingress-pathbased.yaml
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-pathbased
  namespace: default
spec:
  ingressClassName: nginx
  rules:
  - host: tify.kubelancer.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: home-service
            port:
              number: 8080
      - path: /blog
        pathType: Prefix
        backend:
          service:
            name: blog-service
            port:
              number: 8081
      - path: /services
        pathType: Prefix
        backend:
          service:
            name: services-service
            port:
              number: 8082
  • Apply the ingress
kubectl apply -f ingress-pathbased.yaml
  • Get ingress
kubectl get ingress

Output

Validate

Home Page

curl -i  --resolve tify.kubelancer.com:80:192.168.10.0 tify.kubelancer.com

Blog Page

curl -i  --resolve tify.kubelancer.com:80:192.168.10.0 tify.kubelancer.com/blog

Services Page

curl -i  --resolve tify.kubelancer.com:80:192.168.10.0 tify.kubelancer.com/services

Output

Home
Blog
Service
Happy Computing 😄