Menu

Dipesh Majumdar

Blog and Paintings

skeleton ingress to feed nginx ingress controller

The way it works is: 

nginx ingress controller has to be deployed in your nginx namespace which is exclusively reserved for nginx-ingress related stuff.

in that nginx-ingress-controller will have a pod (or more replicas) and a matching service. 

Now individual ingresses for your workloads need to be created so these are then consumed by nginx-ingress-controller pod

To create individual ingress resources one must know to create a skeleton ingress (bare minimum stuff that must go into an ingress) first. So here is syntax of skeleton-ingress:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 name: dipz22-ingress
 annotations:
  nginx.ingress.kubernetes.io/rewrite-target: /
  nginx.ingress.kubernetes.io/ssl-redirect: "false"
 labels: 
   app: ingress
spec:
 rules: 
  - http:
      paths: 
       - path: /
           backend: 
           servicePort: 80
           serviceName: dipz22-service

Go Back

Comment