An OKE cluster for a municipal GIS team was created with a private Kubernetes API endpoint only. What does that imply for how developers run kubectl?
Select an answer to reveal the explanation.
Short Explanation
A private API endpoint is like a locked office phone: it always has a number on your subnet, but you need a badge path—bastion, VPN, or Cloud Shell—to dial in. kubectl still works once that path exists.
Full Explanation
OKE always places a private IP for the Kubernetes API on a subnet you name; you may also assign a public IP when the subnet is public. With a private-only endpoint, kubectl requires network reachability you supply—bastion, VPN, or similar—not a tenancy-wide VCN redesign. The Console is not a substitute for kubectl access, and the endpoint does not relocate regions because it is private.