stackabletech / stackabletech/secret-operator
Configuration overrides for krb5.conf
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
There will be occasions when we will want to add extra configuration to the Kerberos configuration file krb5.conf. An example would be when wishing to include additional realms in the configuration for accessing resources outside of the cluster.
This could be handled by allowing overriding or injection of additional properties to krb5.conf or by allowing the complete replacement of the krb5.conf provided by the Kerberos secret class.
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 by reviewing the Kerberos secret class and how it currently produces krb5.conf. Clarify whether the intended result is property injection or complete file replacement, then define acceptance coverage for adding external realms without breaking the existing configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100