unexport mistakenly-exported kube-proxy constants

[danwinship]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

While working on kubernetes/enhancements#3178 I noticed that several of the iptables chain name variables in kube-proxy were exported variables, leading me to worry that they were being referenced from elsewhere and there would be even more places to clean up that referred to kube-proxy's iptables chains.

But in fact, there aren't. Maybe they used to be shared between kube-proxy and kubelet or something, but right now they're just spuriously exported.

Anyway, since we don't want anyone else using these chains without our knowledge, those constants should be package-local.

Which issue(s) this PR fixes:

none

Does this PR introduce a user-facing change?

NONE

/sig network
/priority backlog

[k8s-ci-robot]

@danwinship: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aojea]

/retest
integration job failures are being investigated

LGTM but defer to Tim since he has the historical context , as mentioned in the description, this chains were kind of an API between kubelet and kube-proxy
/assign @thockin

[danwinship]

as mentioned in the description, this chains were kind of an API between kubelet and kube-proxy

But at least in the current code, they both define their own constants rather than one of them referencing the chain names from the other. And eventually kubelet won't define any of them.

[thockin]

Thanks!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, thockin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/proxy/OWNERS [danwinship,thockin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest