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
I have a service with one nginx canary (internal facing) and multiple kong canaries (external facing, exposing a subset of routes). I see that with nginx traffic management, the "primary" ingress gets a canary ingress automatically.
Is it possible to specify the name of the automatically generated ingress? With a large number of ingresses, it would be very helpful to be able to quickly make sense of which is which without an outlier (as well as track it back to someplace in our help charts).
Is it possible to automatically generate canary ingresses, and control their progression, for other ingresses (i.e., not the "stable" ingress)? It would be nice to be able to gradually roll traffic for both internal and external facing ingresses.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a service with one
nginx
canary (internal facing) and multiplekong
canaries (external facing, exposing a subset of routes). I see that withnginx
traffic management, the "primary" ingress gets a canary ingress automatically.Is it possible to specify the name of the automatically generated ingress? With a large number of ingresses, it would be very helpful to be able to quickly make sense of which is which without an outlier (as well as track it back to someplace in our help charts).
Is it possible to automatically generate canary ingresses, and control their progression, for other ingresses (i.e., not the "stable" ingress)? It would be nice to be able to gradually roll traffic for both internal and external facing ingresses.
Thanks for any feedback.
Beta Was this translation helpful? Give feedback.
All reactions