The HTTP trigger is the only trigger created by default if not configured (by default, it has 1 worker). This trigger handles incoming HTTP requests at container port 8080, assigning workers to incoming requests. If a worker is not available, a 503
error is returned.
Path | Type | Description |
---|---|---|
port | int | The NodePort (or equivalent) on which the function will serve HTTP requests. If empty, chooses a random port within the platform range. |
ingresses.(name).host | string | The host to which the ingress maps. |
ingresses.(name).paths | list of strings | The paths that the ingress handles. Variables of the form {{.<NAME>}} can be specified using .Name , .Namespace , and .Version . For example, /{{.Namespace}}-{{.Name}}/{{.Version}} will result in a default ingress of /namespace-name/version . |
Without ingresseses -
triggers:
myHttpTrigger:
maxWorkers: 4
kind: "http"
attributes:
port: 32001
With ingresseses -
triggers:
myHttpTrigger:
maxWorkers: 4
kind: "http"
attributes:
port: 32001
# See "Invoking Functions By Name With Kubernetes Ingresses" for more details
# on configuring ingresses
ingresses:
http:
host: "host.nuclio"
paths:
- "/first/path"
- "/second/path"
http2:
paths:
- "MyFunctions/{{.Name}}/{{.Version}}"