Permit-API Pods must be reachable as native addresses from a peered VCN that already routes the application subnet. Which OKE network type gives pods routable VCN IPs?
Select an answer to reveal the explanation.
Short Explanation
VCN-native puts each Pod on a pod subnet with a real VCN IP—reachable the same way other VCN addresses are, including from peered VCNs. That is how the app attaches, not a request to redesign hub-and-spoke CIDRs.
Full Explanation
Official VCN-native pod networking attaches pods to a pod subnet so pod IPs are VCN addresses—routable from peered VCNs and on-prem connectivity already available to the VCN. The pod subnet is private. Flannel overlay IPs are not native VCN addresses. LoadBalancer Services and HostNetwork are not substitutes for choosing VCN-native when you need pod IPs on the VCN.