bitnami/sealed-secrets

Tool to help with migration of multiple/all secrets to a new cluster

Open

#365 opened on Feb 26, 2020

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

Repository metrics

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

Description

Some users need to migrate their workload to another cluster. The set of all the manifests of their workload include all the SealedSecret manifests.

Commonly people simply copy the sealed-secret's controller sealing key(s) into another cluster (e.g. following the backup/restore procedures in our docs) and call it a day.

Copying private keys around is a great way to increase your chances of leaking your private key.

There may be a better way: we could create a tool that performs the same task that kubeseal --re-encrypt but by using an arbitrary public key (the one of the target cluster) and in a way that is amenable to be operated in bulk.

Contributor guide

Research direction
Study the kubeseal re encrypt command implementation and design a tool that accepts a target public key and a list of SealedSecret manifests, then re encrypts each item using the target key and outputs the new manifests.
Tech stack
gokubernetes
Domain
backendsecuritydevops
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
GitGoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55