Ambassador support

[ysubach]

Is this a BUG REPORT or FEATURE REQUEST?: Feature request

What you expect to happen: Kubeless will support https://www.getambassador.io/ as a gateway. Following expected to work:

kubeless trigger http create ... --gateway ambassador

Anything else we need to know?: When using Ambassador we do not create actual Ingress resource. Ambassador uses getambassador.io/config annotation defined as part of the Service manifest. More details here: https://www.getambassador.io/reference/advanced

This is different from all currently supported gateways which create separate Ingress resource to direct HTTP traffic to the function.

In my understanding when new HTTP trigger is created for Ambassador we need to edit existing Service definition by injecting proper getambassador.io/config annotation. When trigger is deleted we need to remove this annotation from Service.

Questions:

• Does this sound correct in terms of HTTP trigger support?
• What's the best place to start implementation? So far I'm looking at https://github.com/kubeless/http-trigger/blob/master/pkg/utils/k8sutil.go as a starting point.

[har07]

Hi @ysubach Did you manage to use Ambassador as ingress controller for Kubeless somehow?

[ysubach]

Hi @har07 - unfortunately no, never had a chance to complete it.