default-http-backend is no longer being used, can probably be removed

Bug #1842468 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Worker Charm
Triaged
Low
Unassigned

Bug Description

This commit in Nov 2018 made it where nginx-ingress-controller is no longer using default-http-backend: https://github.com/charmed-kubernetes/charm-kubernetes-worker/commit/cfc85682dbf11db759b3c34ee7370f83fb42ebca#diff-5bbfdf8fd25bb2cc469d297af201bf86L248

It looks like it's no longer necessary since nginx-ingress-controller 0.20.0+ (which we run on all architectures): https://github.com/kubernetes-retired/contrib/issues/1535#issuecomment-444573061

It should be safe to remove default-http-backend. This will allow us to remove a config option (default-backend-image) and reduce the number of images that need to be made available for offline deployments - and clean up some code, too.

George Kraft (cynerva)
Changed in charm-kubernetes-worker:
importance: Undecided → Low
status: New → Triaged
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.