Restrict ClusterRole to readonly IAMIdentityMapping access

[rifelpet]

In the spirit of least privilege security, we shouldn't give write access to the custom resources since it is not needed.

[rifelpet]

/assign @micahhausler

[micahhausler]

I don't think this is quite right, the server updates the status on CRD objects.

[rdrgmnzs]

@micahhausler do you think setting patch & update on IAMIdentityMapping/status would be enough? Give of course that the user has pre-created the identity mappings as IAMIdentityMapping. I skimmed over the 2 PRs that looked related to the CRD change and got a sense that would be enough but would like validation from someone more familiar with the code.

I'm in a fairly security conscious environment and can see giving the application performing authentication the ability to create its own identity mapping becoming an issue very fast.

[rifelpet]

I've updated the ClusterRole to include write access to the status subresource

[rifelpet]

@micahhausler any update on this? just checking in. TY

[micahhausler]

/approve

Can @nckturner take a quick pass and LGTM it?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: micahhausler, rifelpet

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

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

[nckturner]

/lgtm