Skip to content

Consider cleaning up the kube-proxy-clean-up init container #122

Open

Description

How to categorize this issue?

/area networking
/kind cleanup

What would you like to be added:
c92b7ad introduces 2 init containers: cilium-kube-proxy-clean-up and kube-proxy-clean-up. Depending on the value of .Values.kubeProxyCleanup one of the init containers is picked up.
As far as I can see .Values.kubeProxyCleanup is always set to cilium-documentation

# Specifies whether to use the approach documented by cilium or kube-proxy to cleanup the iptables from kube-proxy
kubeProxyCleanup: cilium-documentation

which means that always the 1st init container (cilium-kube-proxy-clean-up) is picked up and used.

Currently I don't see when and how the kube-proxy-clean-up init container would be picked up and used.

Why is this needed:
No need of init container that is never used/rendered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    area/networkingNetworking relatedkind/cleanupSomething that is not needed anymore and can be cleaned uplifecycle/rottenNobody worked on this for 12 months (final aging stage)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions