Ingresses expose Kubernetes applications externally to the public. Ingresses associate with Pods through references to Services. This validator detects a condition when Ingresses are not exposing any application. It can happen if the Ingress rules spec is empty, Services are unresolved, or the Services referenced in the Ingress do not reference an application.
Affected Resources: Ingress
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: my-ingress
spec:
rules:
- http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: my-service
port:
number: 80
apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
type: ClusterIP
selector:
app: non-existing-app-label # There are no apps with such label
...
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.