P5 - Permissions in OKE: the node has identity, and all its pods inherit it
"Kubernetes on OCI at the lowest cost" series — part 5. In part 4 we set up the cluster and node pools. Here's how what's running inside gets permissions on OCI. I'm Matías Galiano, platform architect: I've spent 18 years writing software and 7 designing and operating distributed systems on Kubernetes, with Terraform and GitOps. The entire series is first published on my website, mgaliano.tech.
Matías Galiano, a platform architect, has published the fifth part of his series on "Kubernetes en OCI al menor costo". The article explains how components within a Kubernetes cluster obtain permissions to interact with Oracle Cloud Infrastructure (OCI) APIs. In a Basic cluster, these components use the node's identity, which can lead to any pod on that node having the same permissions.
Galiano describes how he set up the cluster, autoscaler, and External Secrets using Terraform and GitOps, and how he used dynamic groups and policies to manage permissions. The setup uses the node's instance principal, eliminating the need for stored keys and rotation.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.