iac.htora.dev · security templates

Home/Refreshers/Containers on AKS and OKE: refresher

Containers on AKS and OKE

What each service records about a cluster, what a pod can reach on its node, and how to keep the node's disks.

AKSOKE
Audit logOff until a diagnostic setting; kube-audit-admin drops get and listChanges in OCI Audit, 365 days
Keep a nodeAutoscaler and do-not-disrupt annotations, cordonAutoscaler annotation, cordon, pause pool changes
Node disksEphemeral OS disks cannot be snapshottedBoot and block volume backups
Node identity from podsIMDS reachable by defaultInstance principal reachable by default

Commands

AKS: a node's VMkubectl get node <node> -o jsonpath='{.spec.providerID}'
AKS: snapshot a disk elsewhereaz snapshot create -g <evidence group> -n <name> --source <disk id> --incremental true
OKE: a kubeconfigoci ce cluster create-kubeconfig --cluster-id <ocid> --file <path> --token-version 2.0.0
OKE: back up the boot volumeoci bv boot-volume-backup create --boot-volume-id <ocid> --type FULL

Watch out

  • AKS reboots, then reimages, a node NotReady for about 10 minutes. Do not cut the node off.
  • kubectl 1.31 and later sends exec as a get, which kube-audit-admin leaves out.
  • OCI has no termination protection. Node cycling replaces nodes.
Check it worked

A test exec appears in AKSAudit, and a captured node's disks have snapshots or backups tagged with the incident.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.