Security in Managed Kubernetes
Who may do what (IAM), what is recorded, how secrets are encrypted, and who can reach a cluster.
IAM actions
Every operation is checked against your IAM policies. A cluster's resource name is
rn:ews:<region>:<org>:eks:cluster/<cluster id>; permission checks always use the id, also when you
address the cluster by name. Node groups, access entries, add-ons and pod identity associations
have resource names of their own under the cluster.
| Action | Access | What it allows |
|---|---|---|
eks:ListClusters | Read | List Kubernetes clusters |
eks:DescribeCluster | Read | Read a cluster’s configuration, endpoint, version and status |
eks:CreateCluster | Write | Create Kubernetes clusters |
eks:UpdateClusterConfig | Write · destructive | Change a cluster’s settings, such as the networks allowed to reach its API endpoint or deletion protection |
eks:UpdateClusterVersion | Write · destructive | Upgrade a cluster’s control plane to the next Kubernetes minor; its machines are replaced one at a time |
eks:ListClusterSnapshots | Read | List a cluster’s etcd snapshots: when, which revision, how large, verified, kind and expiry |
eks:CreateClusterSnapshot | Write | Take an etcd snapshot of a cluster now (at most one per 10 minutes) |
eks:RestoreCluster | Write · destructive | Restore a cluster’s control plane from one of its etcd snapshots: every Kubernetes object returns to that point, the API is down while the control plane is rebuilt |
eks:PostponeClusterUpgrade | Write | Postpone Deutsche Cloud’s control-plane upgrade of a cluster past its end of support, once, by 14 days |
eks:DeleteCluster | Write · destructive | Delete clusters, their control plane, node groups and nodes |
eks:ListNodegroups | Read | List a cluster’s node groups |
eks:DescribeNodegroup | Read | Read a node group’s configuration, size and nodes |
eks:CreateNodegroup | Write | Add node groups (compute instances that join the cluster) to a cluster |
eks:UpdateNodegroupConfig | Write · destructive | Scale a node group or change its labels and taints; scaling down drains and deletes nodes |
eks:UpdateNodegroupVersion | Write · destructive | Upgrade a node group to the cluster’s Kubernetes minor; its nodes are replaced one at a time, drained first |
eks:DeleteNodegroup | Write · destructive | Delete node groups and their nodes |
eks:ListAccessEntries | Read | List who has an access entry on a cluster |
eks:DescribeAccessEntry | Read | Read an access entry and the access policies associated with it |
eks:CreateAccessEntry | Write | Give an IAM user, group or role an entry on a cluster |
eks:UpdateAccessEntry | Write · destructive | Change an access entry’s Kubernetes username or extra groups |
eks:DeleteAccessEntry | Write · destructive | Remove an access entry, revoking that principal’s access to the cluster |
eks:AssociateAccessPolicy | Write | Grant an access entry an access policy (ClusterAdmin, Admin, Edit, View), cluster-wide or in namespaces |
eks:DisassociateAccessPolicy | Write · destructive | Remove an access policy from an access entry |
eks:AccessKubernetesApi | Write | Get a short-lived token for a cluster’s Kubernetes API (what kubectl uses); the access entries decide what it may do |
eks:ListPodIdentityAssociations | Read | List which service accounts of a cluster act as which IAM roles |
eks:CreatePodIdentityAssociation | Write | Let pods running as a service account act as an IAM role (also needs iam:PassRole on the role) |
eks:DeletePodIdentityAssociation | Write · destructive | Stop a service account’s pods from getting the role’s credentials |
eks:GetClusterAdminCredentials | Write | Break glass: a one-hour cluster-admin client certificate for when Deutsche Cloud sign-in or RBAC is broken; every issuance is recorded |
eks:DescribeAddonVersions | Read | List the managed add-ons Deutsche Cloud offers, their versions and the Kubernetes versions each supports |
eks:ListAddons | Read | List a cluster’s add-ons, the system components included |
eks:DescribeAddon | Read | Read an add-on’s version, options, status and health |
eks:CreateAddon | Write | Install a managed add-on on a cluster (for the DNS add-ons: let it change records in the zones it lists) |
eks:UpdateAddon | Write · destructive | Change an add-on’s version or options; its workloads are rolled |
eks:DeleteAddon | Write · destructive | Remove an add-on’s workloads from a cluster (its CRDs and your resources of them stay) |
eks:GetClusterLogs | Read | Read a cluster’s control-plane logs: the Kubernetes audit log, API server, authenticator, controller manager, scheduler |
Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.
eks:AccessKubernetesApiissues a token, so it is a write. It is only half of getting in: the caller also needs an access entry (see Cluster access).- Handing a role to a node group or a pod identity association also needs
iam:PassRoleon that role. - Installing
external-dns, orcert-managerwith zones, also needsdns:ChangeRecordson every zone listed. - The cluster's own components (load balancers, volumes, DNS add-ons) are not IAM principals; Deutsche Cloud acts for them only on resources that belong to the cluster, or on the zones an add-on lists. Image pulls from your registry are the exception: they use the node group's IAM role.
Audit
Every write that reaches its permission check is recorded in the audit log, allowed or refused. A
read is recorded only when it is refused. A request refused before its permission check, for
example for an unknown cluster (404), records nothing. Changes to a cluster are also
written to its Activity, with who made them: creation, settings, node groups, access entries
and policies, pod identity associations, add-ons, upgrades, snapshots and restores, and every
issuance of break-glass credentials.
Inside the cluster, the Kubernetes audit log is collected by default (see Read control-plane logs).
Encryption
- Kubernetes Secrets are encrypted in etcd with KMS v2; the key-encryption key stays with Deutsche Cloud.
- etcd snapshots are sealed with a key per snapshot under Deutsche Cloud's master key, and cannot be downloaded.
- Volumes of the default StorageClass
ews-volume-encryptedare opened with LUKS on the node; the key is released only to the node the volume is attached to.
Network exposure
- The API endpoint answers on its public address to the networks you allow, inside the network, or both; see Set API endpoint access. Every request authenticates.
- Nodes accept no inbound traffic from the internet until you add rules to the cluster's node security group; see What runs on your machines.
- The control plane reaches kubelets through a tunnel the nodes open (Konnectivity).