Increase nginx-ingress to 0.31.1

Bug #1876724 reported by Jorge Niedbalski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charmed Kubernetes Bundles
Fix Released
Undecided
Kevin W Monroe
Kubernetes Worker Charm
Fix Released
Undecided
Unassigned

Bug Description

[Description]

In order to support the fix required for passing the x-forwarded-proto
HTTP header, fixed upstream here: https://github.com/kubernetes/ingress-nginx/pull/4958
Version 0.31.0 is required, but considering that 0.31.1 contains a subsequent
bug fix, would be recommended to use that version.

This version is also a subsequent change required for https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/54

Revision history for this message
George Kraft (cynerva) wrote :

We will most likely update this in Charmed Kubernetes 1.19 as part of our usual process of updating addons for each release.

Changed in charm-kubernetes-worker:
status: New → Confirmed
milestone: none → 1.19
Changed in charm-kubernetes-worker:
status: Confirmed → Fix Committed
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

I bumped up the 1.19-static image version to match:

https://github.com/charmed-kubernetes/bundle/commit/615028ecc66c821818ec2666d458015cd6294389

This means rocks.c.c will be updated with the new image version once a cdk-addons snap build runs for 1.19:

https://rocks.canonical.com/v2/cdk/kubernetes-ingress-controller/nginx-ingress-controller-amd64/tags/list

Changed in charmed-kubernetes-bundles:
status: New → Fix Committed
assignee: nobody → Kevin W Monroe (kwmonroe)
milestone: none → 1.19
Changed in charmed-kubernetes-bundles:
status: Fix Committed → Fix Released
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.