What happened:
The HTTP Trigger resource creates ingress resources with a fixed set of annotations without option to customize them.
In our setup (see below) this results in the HTTP Trigger resource being unusable as the resulting ingress resource is not handled by any of our ingress controllers.
What you expected to happen:
An option to add or override annotations of the resulting ingress resource, especially "kubernetes.io/ingress.class".
How to reproduce it (as minimally and precisely as possible):
Create a http trigger.
Anything else we need to know?:
We run several nginx ingress controllers, each responsible for publishing to a different network zone. Each ingress controller handles a separate ingress class. There is no default ingress class and there is no "nginx" ingress class.
Environment:
Kubernetes version (use kubectl version): Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Kubeless version (use kubeless version): Kubeless version: v1.0.0-alpha.8
Cloud provider or physical cluster: physical cluster
Is this a BUG REPORT or FEATURE REQUEST?:
Feature Request
What happened: The HTTP Trigger resource creates ingress resources with a fixed set of annotations without option to customize them.
In our setup (see below) this results in the HTTP Trigger resource being unusable as the resulting ingress resource is not handled by any of our ingress controllers.
What you expected to happen: An option to add or override annotations of the resulting ingress resource, especially "kubernetes.io/ingress.class".
How to reproduce it (as minimally and precisely as possible):
Create a http trigger.
Anything else we need to know?: We run several nginx ingress controllers, each responsible for publishing to a different network zone. Each ingress controller handles a separate ingress class. There is no default ingress class and there is no "nginx" ingress class.
Environment:
kubectl version): Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}kubeless version): Kubeless version: v1.0.0-alpha.8