<p>I'm not clear what the difference is between <code>kubernetes_config_map, </code>kubernetes_config_map_v1<code>and</code>kubernetes_config_map_v1_data`?</p>
<p>e.g. <a href="https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/config_map" rel="nofollow noreferrer">https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/config_map</a></p>
<p>Any suggestions?</p>

<p>The <code>v1</code> suffix was recently introduced in the Kubernetes provider (definitely after the <code>alpha</code> provider merge in version 2.4.0) to designate the usage of the Go package for the <code>v1</code> of the Kubernetes API. You can also view resources with the <code>v2</code> suffix for <code>v2</code> of the API. No suffix generally means an alpha or beta version of the API e.g. <code>v1beta1</code>. For example, we see that in the <a href="https://github.com/hashicorp/terraform-provider-kubernetes/blob/main/kubernetes/resource_kubernetes_pod_disruption_budget.go" rel="nofollow noreferrer">resourceKubernetesPodDisruptionBudget</a>, the no suffix designates the usage of <code>v1beta1</code>, and in the <a href="https://github.com/hashicorp/terraform-provider-kubernetes/blob/main/kubernetes/resource_kubernetes_pod_disruption_budget_v1.go" rel="nofollow noreferrer">v1 suffix</a>, the package is the <code>v1</code> API.</p>
<p>As for the difference between <code>_data</code> and no <code>_data</code>, the difference is that the <code>_data</code> manages data within a config map (Update operation) without an import (in fact import is not even supported), and does not enable Create or Destroy operations.</p>
