make use-forwarded-headers a configuration option

Bug #1842286 reported by LP
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Worker Charm
Fix Released
Undecided
Jorge Niedbalski

Bug Description

With nginx ingress controller version 0.22.0 [1], a default of 'false' for use-forwarded-headers was introduced. This is quite a breaking change for clusters with external L7 LBs. I don't consider this configuration to be too exotic.

If we set this in the configuration map of the nginx controller, it'll get overwritten by the next charm update [2]. Please make this a charm option in order to persist it.

[1] https://github.com/kubernetes/ingress-nginx/releases/tag/nginx-0.22.0
[2] https://github.com/charmed-kubernetes/charm-kubernetes-worker/blob/master/reactive/kubernetes_worker.py#L138

Tags: sts
Bui Hong Ha (telescreen)
tags: added: sts
Changed in charm-kubernetes-worker:
status: New → In Progress
assignee: nobody → Jorge Niedbalski (niedbalski)
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :
tags: added: review-needed
Changed in charm-kubernetes-worker:
milestone: none → 1.18
status: In Progress → Fix Committed
tags: removed: review-needed
Changed in charm-kubernetes-worker:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.