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
It would be good if Flagger can support Workloads that depends on Nginx Ingress Controller's Canary annotations.
Basing on the architecture diagram of Flagger, the VirtualService “adjust weight” seems like possible to be also implemented to an Ingress Object that uses Nginx Ingress Controller Class.
The text was updated successfully, but these errors were encountered:
Flagger generates and owns the VirtualService and the ClusterIP services, but for an Ingress object I don't see how would this work without pulling into the Canary CRD the whole Ingress spec.
One option would be to introduce an ingressRef in the Canary CRD that would work similar to the HPA ref. Flagger would use an existing ingress to create the canary clone and adjust the weight for progressive delivery or the header/cookie for A/B testing.
Nginx doesn't report metrics for canaries kubernetes/ingress-nginx#4026 so Flagger can't have built-in checks for HTTP errors or latency. The apps must be instrumented and custom metrics checks must be used.
It would be good if Flagger can support Workloads that depends on Nginx Ingress Controller's Canary annotations.
Basing on the architecture diagram of Flagger, the VirtualService “adjust weight” seems like possible to be also implemented to an Ingress Object that uses Nginx Ingress Controller Class.
The text was updated successfully, but these errors were encountered: