why using kubectl_manifest instead of kubernetes_manifest?

[victor-keltio]

Hey there, thanks for this plugin, I've been using it a lot.

But! As perfect as it is, I don't really understand why we have to use 2 providers (resp. kubernetes and kubectl).
For the former, it's kinda obvious, but for the latter, why use kubectl_manifest instead of kubernetes_manifest?

Thanks a lot :)

[bohdantverdyi]

Hi, I fully understand.

However, kubernetes_manifest doesn't allow you to plan/apply on CRD resources that are not yet created.

Therefore, when using only the provider kubernetes, we have to disable cluster issuer resources first, apply the Helm chart that creates the CRD, and then apply the cluster issuers.

This is inconvenient, and companies that use pipelines for Terraform runs will need to create two PRs.

It's a known issue, and there has been an open issue on GitHub for the Kubernetes provider for a few years already.

I even already implemented this in another branch you could check it, but I am waiting feature which will allow CRD validation during apply/plan

[bohdantverdyi]

hashicorp/terraform-provider-kubernetes#1367

Issue opened 3 years ago for it )

[victor-keltio]

Okay! I haven't thought about the CRD definition then the resource creation; this explains the kubectl provider.
Thanks a lot for these explanations, I guess we have to wait for this heh. :)