dragonflydb
dragonfly operator namespace override
Did you search GitHub Issues and GitHub Discussions First? Many users may find their feature is already being discussed. Help us keep duplicates to a minimum by searching for your feature first to see if it is already in progress.
Yes, I did not find any discussion, however there was one ask in an issue (2007) that wanted to know the documented field to change for the dragonfly operator to run in a different namespace back a few years...with no response.**
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We want all of our proxies, database instances and operators to be in the same namespace for management.
Describe the solution you'd like A clear and concise description of what you want to happen.
In the template, add a 'namespaceOverride' and any logic in the chart to pull from the values.yaml
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
