You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extend the configs override annotations to work at the namespace level. This will allow proxy configs to be overridden for all workloads in a namespace, so that the users won't have to repeat the annotations on each workload.
Following our discussion in #2497, we've decided to exclude this feature from that PR, until we see a realistic use for it.
How should the problem be solved?
Update the conf.getOverride() method to look up any namespace annotations, if no pod-level annotations are present.
How would users interact with this feature?
Specifying the config annotations in the namespace's metadata.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
Feature Request
What problem are you trying to solve?
Extend the configs override annotations to work at the namespace level. This will allow proxy configs to be overridden for all workloads in a namespace, so that the users won't have to repeat the annotations on each workload.
Following our discussion in #2497, we've decided to exclude this feature from that PR, until we see a realistic use for it.
How should the problem be solved?
Update the
conf.getOverride()
method to look up any namespace annotations, if no pod-level annotations are present.How would users interact with this feature?
Specifying the config annotations in the namespace's metadata.
The text was updated successfully, but these errors were encountered: