An Ingress in namespace permits references backend Service permit-ui, but that Service only exists in namespace libraries. Typical CKAD-style Ingress backends fail. What should the developer do?
Select an answer to reveal the explanation.
Short Explanation
Ordinary Ingress backends look next door in the same namespace. If permit-ui lives in libraries, move the Ingress there too—or use an explicit platform feature for cross-namespace, not a made-up ClusterIngress kind.
Full Explanation
Standard Ingress backend Service references are namespaced with the Ingress. Referencing a Service that exists only in another namespace typically fails unless a controller-specific or Gateway API cross-namespace pattern is intentionally used. The usual fix is to place Ingress and Service together. There is no core ClusterIngress kind or hostNetwork field on Ingress that magically cross-wires namespaces.