Unresolved Service reference in Ingress

Ingresses expose Kubernetes applications externally to the public. Ingresses associate with Pods through references to Services. This validator detects a condition when Ingresses are pointing to non-existing Services. It usually indicates a naming error in the Ingress or Service.

Affected Resources: Ingress

Examples

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-ingress
spec:
  rules:
  - http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: foo-service    # Service not found
            port:
              number: 80

apiVersion: v1
kind: Service
metadata:
  name: bar-service              # Different name in Ingress
...

Resolution

Check if the Service is present in the same namespace.

Check if the Service is present in a different namespace. Kubevious Search can be a very handy tool to find Services across namespaces. You cannot mount a Service from a different namespaces. In that case you would need to create a Service in namespace where the Ingress resides.

Did you make a typo in the Ingress? Kubevious Search uses fuzzy logic to return results and can help with finding the correct Service.

Make necessary naming corrections on the Ingress or the Service.

Learn More

https://kubernetes.io/docs/concepts/services-networking/ingress/

https://kubernetes.io/docs/concepts/services-networking/service/

Unresolved Service Port reference in Ingress

Storage

Need other validation rules?

Please let us know if there are other built-in validation rules you would like to see in Kubevious to detect misconfigurations and violations to best practices. Optionally, you can provide your details so we can reach out to you with follow-up questions.

Share this article on: