six-group / six-group/haproxy-operator
A question about maps
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29
- Forks
- 9
- Avg merge
- 23h 55m
- Merged PRs (30d)
- 16
Description
Acording to the README file, it is possible to use maps but in the example given the map files are assumed to be there.
Now, there are a couple ways to get maps but the most simplest might be just updating the map files (for example, updating a configmap from which a projected volume is created) and then triggering a reload, so I was wondering if there are any plans to add a functionality to handle maps so that any change in them produces a reload. If not, do you know of any solution that we could use?
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 README example and the operator's handling of map files, ConfigMaps, projected volumes, and reload triggering. Determine whether map changes can be watched and reloaded, and document the supported behavior or the required design and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100