envoyproxy / envoyproxy/gateway
Support or default to and allow configuration of the name of the mutating resource
- Dominant language
- Go
- Stars
- 3k
- Forks
- 864
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 140
Description
*Description*:
Standard global resource name uniquifying puts the namespace on the front of the name - this system (not just the helm charts, but the code itself) ONLY handles it on the end with a `.` separator and no configuration options are available via env or arg to tell the job where to find it. It just always looks for it on the end which is the wrong place according to convention.
Thanks for considering this issue. Happy to help contribute if it's an acceptable change.
Or even scan through all four possible reasonable options for a mutate resource?
ns.name
name.ns
ns-name
name-ns
Can't be anything else (reasonably).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.