Ingress is not attaching to load balancer if the ingress file is having configuration snippet

[PRYeswanthReddy]

Ingress is not attaching to load balancer if the ingress file is having configuration snippet

For example:

if ingress is having the below annotation, the ingress is not getting a load balancer.

nginx.ingress.kubernetes.io/configuration-snippet: >
  more_set_headers "Strict-Transport-Security : max-age=31536000;
  includeSubDomains;";

This happened after upgrading from 4.11.0 to 4.12.1 , if we remove that annotation the loadbalancer is getting attached.

i was going through some documentations and could see that setting this annotation-risk-level to critical will solve this issue, is this okay to bypass using this annotation? if we use this annotation at controller level will there be any security issues?

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[PRYeswanthReddy]

if we have configuration-snippet in annotations of specific ingress, do we need to set the annotations-risk-level: Critical?

Will this annotation will be removed in future?

[Gacko]

Please read the release notes of v1.12.0. You will need to set annotations-risk-level: Critical to re-enable snippet annotations.