Ingress
Reference for the humanitec/ingress driver
Property | Description |
|---|---|
Resource Type | |
Account Type | None |
Name | Type | Description |
|---|---|---|
api_version | string | [Optional] The API version of the ingress object to produce. Must be one of v1beta1 or v1 . Defaults to v1 |
class | string | [Optional] The ingress controller class. Will be inserted as an annotation or in the ingressClassName property depending on api_version. |
annotations | object | [Optional] An object with values of type string that will be inserted as annotations on the generated Ingress object. |
labels | object | [Optional] An object with values of type string that will be inserted as labels on the generated Ingress object. |
no_tls | boolean | [Optional] Does not generate a TLS section even if a tls_secret_name is supplied. Useful if TLS termination happens on the Load Balancer. |
tls_secret_name | string | [Optional] Overrides the Humanitec provided secret. Useful if secrets are injected by another mechanism e.g. Cert Manager or Rancher. |
None
If
class is omitted, then the generated ingress object will not have an ingress class defined. See Default Ingress Class in the Kubernetes documentation for possible behaviours.To create a resource definition that adds NGINX specific annotations to generated ingress objects in the
development environment type:curl https://api.humanitec.io/orgs/${HUMANITEC_ORG}/resources/defs \
-X POST \
-H "Authorization: Bearer ${HUMANITEC_TOKEN}" \
-H "Content-Type: application/json" \
--data-binary '
{
"id": "custom-ingress",
"name": "Custom Ingress",
"type": "ingress",
"criteria": [
{
"env_type": "development"
}
],
"driver_type": "humanitec/ingress",
"driver_inputs": {
"values": {
"api_version": "v1",
"class": "nginx",
"annotations": {
"nginx.ingress.kubernetes.io/rewrite-target": "/$2",
"nginx.ingress.kubernetes.io/cors-allow-headers": "Keep-Alive,Authorization"
}
}
}
}'
Last modified 11mo ago