Adding missing efs policy statements DescribeAvailabilityZones, Descr…

[daniel-pebble]

This PR aligns the efs provider IAM policy with the reference policy found here
https://raw.githubusercontent.com/kubernetes-sigs/aws-efs-csi-driver/master/docs/iam-policy-example.json

Without this, when provisioning a dynamic volume the user may see this error.

[elamaran11]

LGTM. @shapirov103 Please check and run e2e

[shapirov103]

/do-e2e-tests

[aws-ia-ci]

end to end tests failed. A maintainer can provide more details.

[shapirov103]

@elamaran11 it maybe unrelated to the applied code change but I am getting the following error on e2e:

blueprint-construct-dev | 10:03:24 PM | CREATE_FAILED | Custom::AWSCDK-EKS-KubernetesResource | blueprint-construct-dev/adot-collector-sa/manifest-adot-collector-saServiceAccountResource/Resource/Default (blueprintconstructdevadotcollectorsamanifestadotcollectorsaServiceAccountResourceA34512D7) Received response status [FAILED] from custom resource. Message returned: Error: b'Error from server (NotFound): error when creating "/tmp/manifest.yaml": namespaces "adot" not found\n'

Do we have dependencies properly defined in ADOT?

[shapirov103]

/do-e2e-tests

[elamaran11]

@elamaran11 it maybe unrelated to the applied code change but I am getting the following error on e2e:

blueprint-construct-dev | 10:03:24 PM | CREATE_FAILED | Custom::AWSCDK-EKS-KubernetesResource | blueprint-construct-dev/adot-collector-sa/manifest-adot-collector-saServiceAccountResource/Resource/Default (blueprintconstructdevadotcollectorsamanifestadotcollectorsaServiceAccountResourceA34512D7) Received response status [FAILED] from custom resource. Message returned: Error: b'Error from server (NotFound): error when creating "/tmp/manifest.yaml": namespaces "adot" not found\n'

Do we have dependencies properly defined in ADOT?

I dont think we have touched ADOT in a while. Let me take a closer look tomorrow.

[aws-ia-ci]

end to end tests failed. A maintainer can provide more details.

[shapirov103]

LGTM

[shapirov103]

merging, will address any issues after moving to CDK 2.114 and EKS 1.28

will be addressed in the next PR