-
Story
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
We should deprecate spec.proxy.concurrency and point users to use the ProxyConfig API
Acceptance Criteria:
- In 2.4, it should not be possible to set spec.proxy.concurrency (validation fails, message pointing to ProxyConfig API)
- Upgrades to 2.4 should fail if the field is set (again, pointing out to use ProxyConfig API)
- (optional) in 2.3.1 we should emit a warning
1.
|
Warn users about deprecation of spec.proxy.concurrency | Backlog | Unassigned |