Kubernetes-ingress: No annotation for `nginx.org/http-snippets`?

Created on 29 Mar 2018  路  4Comments  路  Source: nginxinc/kubernetes-ingress

Greetings,

Is there a reason for not having an annotation for http-snippets via nginx.org/http-snippets?

EDIT:

Specifically, I'm referring to https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization

enhancement

Most helpful comment

@jaytaylor yes, most of the time to customize an Ingress you would want to change the location or server context. What is your use case?

the http is a global context that includes all the upstreams and servers of all the Ingress resources. In general, changing this context will affect all the Ingress resources. That is why there is no annotation, only a configmap key.

All 4 comments

@jaytaylor yes, most of the time to customize an Ingress you would want to change the location or server context. What is your use case?

the http is a global context that includes all the upstreams and servers of all the Ingress resources. In general, changing this context will affect all the Ingress resources. That is why there is no annotation, only a configmap key.

The use-case is to fix incorrect outbound location headers generated due to a misbehaving upstream LB out of my control.

I'll open an issue the official k8s nginx ingress instead, as that is what comes with kubernetes by default, and the default configuration between nginxinc's version and the k8s version is very different.

This can be accomplished through custom templates.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

toddams picture toddams  路  6Comments

Uter1007 picture Uter1007  路  5Comments

crossdot picture crossdot  路  3Comments

RazaGR picture RazaGR  路  6Comments

muradmomani picture muradmomani  路  7Comments