CODEWITHSUNDEEP
kubernetesk8s-cluster-role
Dragos Cazangiu
Dragos Cazangiu

Reputation: 157

Why does Kasten require cluster-scoped read operations on Secrets?

We have installed Kasten backup solution on our kubernetes cluster and I noticed that the clusterRole "kube10-admin" has the access on all resources with all verbs (*).

As a central Kubernetes management team in an organization, we would like to give restricted access for Secrets, and just wanted to get an idea around what's the use-case which the operator is supporting.

Why does it need cluster wide access to secrets? Couldn't it just have roles with access to the specific namespaces that it does the backup for?

Upvotes: 0

Views: 46

Answers (1)

Daya Frenkiel
Daya Frenkiel

Reputation: 1

Kasten (or K10) is designed to backup the whole cluster from end-to-end. This includes the cluster state (ETCD/nodes) and the app data (internal or external). The ability to preform this robust backup will always be possible, even if you choose to configure it to work only on specific resources. For this reason K10 needs access to EVERYTHING on your cluster, even if you only want to backup a single resource (yes, including secrets).

Another reason is the transformation ability K10 offers: when restoring or cloning a cluster you can change it's configuration (storage type etc...). For that it needs write permissions on all resources.

This can seem quite scary at first, but using an external backup solution will always need to be from a vendor you trust exactly for these reasons.

Upvotes: 0

Related Questions