stackabletech / stackabletech/secret-operator
Split provisioning into a separate service
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
As discussed in #5, we would eventually like to split the sensitive key provisioning (TLS signing, Kerberos keygen) into a separate service to avoid exposing sensitive key material.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #5 and the provisioning paths for TLS signing and Kerberos key generation. Define the separate service boundary and how sensitive key material will remain isolated before making changes. Done means provisioning is handled by a separate service without exposing sensitive key material.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100