Support for ambassador ingress

[jdamata]

I think all that is needed is to have ambassador annotations added to the primary service which would direct traffic to both the primary service and canary service based on weight.

https://www.getambassador.io/docs/dev-guide/canary-release-concepts/#flexible-kubernetes-canary-releases-smart-routing-with-ambassador

Ref: https://github.com/weaveworks/flagger/issues/67 https://github.com/weaveworks/flagger/issues/49

[stefanprodan]

Does Ambassador have a go client and CRD?

[jdamata]

Nope, theres talk of it in https://github.com/datawire/ambassador/issues/482.

[cdbyrd]

So thinking about this in a different way, if you have ambassador in front of istio, serving as the API Manager and cluster ingress, the service definition is separate and behind that (no standard ingress controller/gateway and ingress resources). If you did a canary deployment against the service definition, it seems like that would work. You wouldn't need to touch ambassador if you didn't use it for canary definition and just used flagger as that tool to manage istio.

[trash-anger]

Hi, Here's an update about ambassador which now have both CRD (datawire/ambassador#482) and and client go.

[RTodorov]

@stefanprodan can we remove the upstream-blocked label? also, is there a recommendation on how to use flagger to orchestrate canary while having Ambassador as the api-gateway?

[stefanprodan]

@RTodorov can you point me to the go clientset package?

[ghost]

@RTodorov Is this something you are looking for? https://github.com/datawire/ambassador/tree/master/go

[jonathanmccracken]

any progress on supporting Flagger with Ambassador?

[olemarkus]

I would also be very interested in this

[klemmster]

Hey there, is there any update on this?