stackabletech / stackabletech/secret-operator
Distinguish TLS common names?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
https://github.com/stackabletech/kafka-operator/issues/724 shows that we don't really have a good way to identify a "machine user" that others can write authorization rules against. You could use the SANs we already set, but that can as often just identify the instance, rather than the app/group of instances (such as StatefulSet).
Perhaps it would make sense to use the pod's ServiceAccount? That said we should probably avoid the format serviceaccount.ns to prevent people confusing them with DNS names.
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 the linked kafka-operator issue and review how this operator currently identifies workloads through TLS SANs. Define whether a ServiceAccount-based identity or another common-name convention should support authorization rules, and document the chosen identity format and its implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100