What's the difference between Terraform's kubernetes_config_map and kubernetes_config_map_v1 and kubernetes_config_map_v1_data?

Question

I'm not clear what the difference is between kubernetes_config_map, kubernetes_config_map_v1andkubernetes_config_map_v1_data`?

e.g. https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/config_map

Any suggestions?

Answer 1

The v1 suffix was recently introduced in the Kubernetes provider (definitely after the alpha provider merge in version 2.4.0) to designate the usage of the Go package for the v1 of the Kubernetes API. You can also view resources with the v2 suffix for v2 of the API. No suffix generally means an alpha or beta version of the API e.g. v1beta1. For example, we see that in the resourceKubernetesPodDisruptionBudget, the no suffix designates the usage of v1beta1, and in the v1 suffix, the package is the v1 API.

As for the difference between _data and no _data, the difference is that the _data 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.