Dmytro Zavalkin

@longwuyuan I'm sorry but your request is not relevant. I provided output of `curl localhost:10246/configuration/backends` command which clearly shows that there is no upstream created for `webclient-prod2` service (`"noServer": true`).

Yes, this is setup we wanted to use for our PROD environment but unfortunately we couldn't, since canary ingress makes service it is pointed to unusable for any other ingress....

@longwuyuan VIP is just a name for (sub)domain, we can name it "main" instead. The idea is to switch (sub)domain from one service to another in blue/green manner (similar to...

Not really, basically we want to have both services `webclient-prod1` and `webclient-prod2` to be always exposed on their own subdomains (ingresses) `webclient.prod1.domain.com` and `webclient.prod2.domain.com` and have another **main/VIP/you name it**...

I don't understand how this can be a new feature and not a bug. Service used in a canary ingress can't be used in any other ingress - how come...

Nope, unfortunately I don’t know how to workaround this without switching to another ingress controller…Best regards,Dmytro On 14 Nov 2023, at 15:21, Yannick Stevenin ***@***.***> wrote: @Zyava hello! did you...

Benefits are evident: - No file name lookup over the include path at all, just file include, with opcache it means no disk access at all - With APC/ZendPtimizer generated...