Ingress creates wrong firewall rule after default-http-backend service was clobbered.

[bowei]

From @MrHohn on December 8, 2016 18:46

From kubernetes/kubernetes#36546.

During development, found ingress firewall test failed instantly on my cluster. Turned out due to some reasons, the default-http-backend service was deleted and recreated, and it was then allocated a different nodePort. Because ingress controller records this nodePort at the beginning but never refresh(ref1 and ref2), it always create firewall rule with the stale nodePort after.

@bprashanth

Copied from original issue: kubernetes/ingress-nginx#48

[bowei]

From @bprashanth on December 9, 2016 0:23

The assumption is it doesn't change, and it typically shouldn't because it exists in the kube-system namespace, do you remember why it was deleted ? Since it can totally get deleted by the user, we should periodically reconciling the default backend.

[bowei]

From @MrHohn on December 9, 2016 0:36

I accidentally deleted all kube-system services while doing experiment on addon manager, not kubernetes's fault.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[nicksardo]

/lifecycle frozen

[nicksardo]

Dupe #184
/close