Contact Details (optional)

No response

Summary

storage class is implemented with:
kubectl_manifest

and this terraform provider can be avoided and we can use the hasicorp one:

resource "kubernetes_storage_class" "storage_class" {
  metadata {
    name = var.storage_class_name
  }
  storage_provisioner = "efs.csi.aws.com"
  depends_on = [helm_release.kubernetes_efs_csi_driver]
}

I think that could be the solution but I am not totally sure:

Motivation

When using continuous integration for deploying terraform infrastructure...
kubectl is not configured to connect with the eks cluster but using the terraform kubernetes provider is better because that provider is properly configured to use the token and certificates from eks terraform objects.

I will try to do a PR soon.

Alternatives

No response

Additional Context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct