bitnami/sealed-secrets

Feature Request: Multiple key support

Open

#120 opened on Oct 23, 2018

View on GitHubContributor guide
 (9 comments) (7 reactions) (0 assignees)Go (771 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (9,222 stars)
PR merge metrics
 (PR metrics pending)

Description

We have many kubernetes clusters. For lots of secrets, we encrypt them per-cluster, as they're unique to that cluster.

For some secrets, we would like to encrypt them once, and have all clusters be able to decrypt those secrets. Examples might be, the newrelic or pagerduty API keys. Each cluster would have the dynamically generated key that's unique to it, and we would like to use that key to encrypt the global decryption key.

This could be modelled by allowing SealedSecrets to optionally reference a different decryption key, potentially?

Contributor guide

Research direction
Explore the current key management in sealed secrets to understand how to support multiple decryption keys per cluster without breaking existing functionality.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60