Inspectors’ dispatch workloads run on an OKE cluster. How should developers manage those workloads day to day?
Select an answer to reveal the explanation.
Short Explanation
OKE hands you a kubeconfig; kubectl talks to that cluster’s API. That is the developer path—not SSH into workers to start apps. IAM plus Kubernetes RBAC still gate who can do what.
Full Explanation
Developers manage OKE workloads with standard Kubernetes tooling. OKE produces kubeconfig that points kubectl at the cluster API endpoint; access is governed by OCI IAM and Kubernetes RBAC. SSH to workers to start application processes bypasses the orchestrator. Object Storage zip polling and /etc/hosts hacks are not the supported management path.