kubernetes-sigs/cluster-api

Service Account Private Key Rotation

Open

#7,456 opened on Oct 25, 2022

View on GitHub
 (6 comments) (2 reactions) (0 assignees)Go (1,532 forks)auto 404
help wantedkind/featurekind/proposallifecycle/frozenpriority/backlogtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

User Story

As a developer I would like to setup a rotation mechanism service account private keys for security. Rotating RSA-2048 keys is essential if I use the SA key to sign projected service-bound tokens.

Detailed Description

I would like CAPI to:

  1. Create the new key pair.
  2. Allow the user to create a mechanism in which it can intercept the newly generated key-pair so it can update internal systems before it is rolled out.
  3. Run machine repave with no downtime. (eg publishing public key first and then private key through 2 machine repaves).

Anything else you would like to add:

N/A

/kind feature

Contributor guide

Research direction
Investigate how Cluster API manages service account key rotation; look at existing key management patterns in Kubernetes, especially projected service account tokens. Study the machine repave process in Cluster API and how to introduce a key rotation mechanism without downtime. Start by examining the Cluster API codebase for existing key handling logic (e.g., in controllers for clusters or machines).
Tech stack
go
Domain
backendinfrastructuresecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesCluster API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20