Trim down the worker iam role

[rajatchopra]

The kubelet was suspected to use attach/detach volume and load balancer apis, but
apparently not. We can trim the privileges down to minimum now.
The last big one remaining is DescribeInstances that is stuck because of instance 'tags'.

The cluster comes up just fine, now hoping I didn't miscalculate on actual workloads.. time for the virtuous e2e to shine.

Part 2: Try removing s3 access also and see what gives.

[wking]

This looks fine to me (and I expect e2e to pass, but am happy it's there just in case ;). Should I /lgtm now, or do you plan on iterating here until you have the worker all tightened up? What about the master and bootstrap configs (bootstrap may need to retain more than masters, at least S3 get for the bootstrap Ignition config).

[openshift-ci-robot]

@rajatchopra: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-openstack	4dfd6f7	link	/test e2e-openstack
ci/prow/e2e-libvirt	4dfd6f7	link	/test e2e-libvirt

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.

[rajatchopra]

This looks fine to me (and I expect e2e to pass, but am happy it's there just in case ;). Should I /lgtm now, or do you plan on iterating here until you have the worker all tightened up? What about the master and bootstrap configs (bootstrap may need to retain more than masters, at least S3 get for the bootstrap Ignition config).

Lets get this through. I will check with S3 permissions and put another PR about it - don't want to pile it on without basic evidence for it.
We plan to keep Masters and Bootstrap as it is for now - bootstrap is shortlived, and cleaning up master is a longer task. At least with this we have reduced the attack surface.

[wking]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rajatchopra, wking

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 [rajatchopra,wking]

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