A partner system outside the OKE cluster must reach a Service via a port on worker nodes. Which Service type publishes that node port, and how should teams treat it as a public front door on OKE?
Select an answer to reveal the explanation.
Short Explanation
NodePort hangs the Service on a port on every worker—like side doors on each building. Handy as an escape hatch or for some ingress paths, but not the usual preferred public front door on OKE compared with a LoadBalancer Service.
Full Explanation
NodePort exposes a Service on a static port on each node. It is useful when something outside must hit a node address and is involved in some flannel ingress paths, but it is not the preferred everyday public exposure on OKE. ClusterIP stays internal; Ingress still fronts Services; ExternalName does not provision OCI load balancers.