Kubernetes Ingress and Externals

11/05/21 19:47 Filed in: Systems Administation
My microk8s decided to update its Ingress component. While trying to be helpful this actually disabled my redirections to internal web sites. The reason for the failure was that the syntax for configuring the externals has changed.
The fix is simple rewrite the old v1beta1 format into v1 format:

ie take this:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: external-service
spec:
  rules:
  - host: atum-ra.castro.aus.net
    http:
      paths:
      - backend:
          serviceName: atum-ra-http
          servicePort: 80
        path: /

and make it look like this:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: external-service
spec:
  rules:
  - host: atum-ra.castro.aus.net
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
             name: atum-ra-http
             port:
               number: 80

A few minutes of text editing later all fixed.

Unfortunately you have to ignore the fact that the log files still talk about v1beta1 when external-service is mentioned on loading.

Tags: