Closed roni-frantchi closed 3 months ago
@yaronya can we close this issue?
No not yet, See comment in #9:
haven't removed the kubectl provider yet because customer use it and they need it to make the transition - otherwise kubectl resources would fail on destroy
There's no upgrade path to the new version of this module and we don't use gavinbunney/kubectl
in it.
No good reason to use a 3rd party here.
It is only ever used to create the
storage_class
andcsi_service_account
using yaml instead of HCL, but the equivalent HCL can be used inhashicorp/kubernetes
or even yaml combined withyamldecode()
.We could easily make the swap and drop this 3rd party dep.