OpenLiberty / OpenLiberty/guides-common
Guide for reading Kubernetes config in as Liberty config variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 6
- Avg merge
- 2h 12m
- Merged PRs (30d)
- 1
Description
Related to: https://github.com/OpenLiberty/open-liberty/issues/9786
Variable are automatically read from a location on the file system (the default is /bindings.) A guide could either focus on the service binding operator ( which will automatically map kubernetes secrets to /bindings) or show secrets mapped to the files system via a volume mount.
Contributor guide
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 reading related issue #9786 and reviewing how Liberty reads variables from /bindings. The guide should explain either the Service Binding Operator mapping Kubernetes secrets there or mapping secrets through a volume mount, with one approach documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100