Automated cherry pick of #8497: Mark dns-controller and kops-controller as non-root

[johngmyers]

Cherry pick of #8497 on release-1.17.

#8497: Mark dns-controller and kops-controller as non-root

For details on the cherry pick process, see the cherry pick requests page.

[mikesplain]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, mikesplain

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 [mikesplain]

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

[johngmyers]

/retest

[geojaz]

/lgtm

[johngmyers]

/retest

[rifelpet]

I don’t think the PR that changed the kops-controller user was cherrypicked to 1.17

https://github.com/kubernetes/kops/blob/release-1.17/cmd/kops-controller/BUILD.bazel

[johngmyers]

Ah, so many patches.
Do we want to cherrypick the user changes to 1.17? In any case we won't be able to cherrypick this until there is an intervening release.

[k8s-ci-robot]

@johngmyers: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kops-e2e-kubernetes-aws-1-17	32d58b6	link	/test pull-kops-e2e-kubernetes-aws-1-17

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[rifelpet]

I have no opinion on whether we cherry-pick it. Luckily the hostPath logging work was never cherry-picked back to 1.17 or 1.16 so we don't need to worry about cherry-pick the revert if we do choose to cherry-pick the user change PR and this.