Menu

Kubernetes Secrets Are Distribution, Not Custody
📰

Kubernetes Secrets Are Distribution, Not Custody

DEV Community: kubernetes·Zen Mesh Inc.·11 days ago
#AcVK2gYb
#devtokubernetes#devto#dev#secret#custody
Reading 0:00
15s threshold

This is article 4 of 10 in Beyond Kubernetes Defaults . Read article 3: A Kubernetes Lease Is Not a Fencing Token first, or start with article 1: When Kubernetes Primitives Aren’t Enough . Later articles cover workload admission and more.

Kubernetes Secrets are not the villain of this article.

They are a useful API for delivering sensitive configuration to workloads, and they can be protected with encryption at rest, RBAC, admission controls and careful operational practice.

The mistake is asking a Secret to answer security questions that are outside its job.

The overloaded-secret problem

A system often starts with a simple pattern:

create credential -> store credential in Secret -> mount Secret into Pod -> possession means caller is trusted

Enter fullscreen mode

Exit fullscreen mode

That can work.

Over time, however, "the Secret" can begin representing several different concepts simultaneously:

identity;

authorization;

enrollment state;

key custody;

tenant context;

rotation…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.