stackabletech / stackabletech/secret-operator
Allow the configuration of multiple KDCs
Open
Nobody has claimed this yet.
customer-request
type/feature-improvement
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Only one KDC can be set in a SecretClass:
---
apiVersion: secrets.stackable.tech/v1alpha1
kind: SecretClass
spec:
backend:
kerberosKeytab:
kdc: KDC1.MY.REALM.COM
In a krb5.conf, multiple KDCs can be given:
[realms]
MY.REALM.COM = {
kdc = KDC1.MY.REALM.COM
kdc = KDC2.MY.REALM.COM
}
To support high availability, it should be possible to also define multiple KDCs in a SecretClass.
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 SecretClass.spec.backend.kerberosKeytab.kdc field and trace how its value is handled for krb5.conf configuration. Determine the existing validation and configuration path, then verify that multiple KDC entries can be defined and provide high availability without breaking the single-KDC form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100