Cherry-pick #1209 [Expose custom health check ports in the firewall] into release-1-9

[spencerhance]

Also includes the commit from #1084 in order to cherry-pick in the e2e tests as well

[k8s-ci-robot]

Hi @spencerhance. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[spencerhance]

/assign @rramkumar1

[rramkumar1]

@spencerhance Let's keep the cherry pick clean. Can you send a separate PR for the test.

[spencerhance]

@rramkumar1 Sure thing. Should I just include 007bf05 and not include 54885c3 from the original PR?

[rramkumar1]

The cherrypick should only contain the same commits from the corresponding PR which was merged to HEAD.

[spencerhance]

Hmm okay. I don't see a reasonable way to cherry-pick both commits from #1209 without including bowei's e2e stuff. I can just cherry-pick 007bf05 and not include the other commit in this PR.

[rramkumar1]

/lgtm

[rramkumar1]

/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rramkumar1, spencerhance

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:

• OWNERS [rramkumar1]

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