Release v1.2.0

[wongma7]

Is this a bug fix or adding new feature?

What is this PR about? / Why do we need it? this is a cherry-pick of #368 on master to update docs and such now that the images from #368 have been pushed

also #371 to make the helm chart and kustomize match the changes in release-1.2

Also I updated the kustomize install in README, missed that the first round.

What testing is done?

[wongma7]

/hold

unhold when #371 merges.

then v1.2.0 will release 100%. we are 99% of the way there since there is a GitHub release but these readme updates aren't in amster branch yet..

[jqmichael]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jqmichael, wongma7

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 [jqmichael,wongma7]

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

[wongma7]

/hold cancel

[wongma7]

/test pull-aws-efs-csi-driver-e2e

failure is worrisome

[wongma7]

[Fail] [efs-csi] EFS CSI [Driver: efs.csi.aws.com] [It] should continue reading/writing without hanging after the driver pod is restarted
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:303
[Fail] [efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Pre-provisioned PV (default fs)] volumes [It] should store data
/home/prow/go/pkg/mod/k8s.io/[email protected]/test/e2e/storage/utils/utils.go:83

/retest

need kubernetes-sigs/aws-ebs-csi-driver#802 for debugging

[wongma7]

Also, the driver restart test coudl mess with log-collecting anyway depending on order it is run since logs from before the test would disappear.

[kbasv]

/test pull-aws-efs-csi-driver-e2e

[kbasv]

/test pull-aws-efs-csi-driver-e2e

[kbasv]

/test pull-aws-efs-csi-driver-e2e