Ingress Controller - Route does not have a name. decK needs routes to be named

#1

After upgrading to ingress-controller 0.4.0 I started seeing “route ‘{UUID}’ does not have a name. decK needs routes to be named.” Errors.

I think this refers to the naming of a route with the Ingress definition but I fail to see how I’d name the route using the Ingress definition

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kong-wallet-openapi-ingress
  namespace:  default
  annotations:
    kubernetes.io/ingress.class: "kong"
    configuration.konghq.com: kong-wallet-ingress
    plugins.konghq.com: wallet-openapi-key-auth, wallet-openapi-acl, wallet-openapi-rewrite
spec:
  tls:
    - hosts:
        - ${KONG_AWS_DNS}
      secretName: ${KONG_AWS_CERT_NAME}
  rules:
    - host: ${KONG_AWS_DNS}
      http:
        paths:
          - path: "/api/wallet/openapi"
            backend:
              serviceName: wallet
              servicePort: http
#2

@davideagle To upgrade to 0.4.0, you will need a fresh installation, meaning you will need a database which is not populated by 0.3.0. You can spin up a new Kong Ingress cluster, cut the traffic over and then decommission the old one.