Adding documentation for the secret_v1_data resource

Author: jaylonmcshan19-x

docs/resources/secret_v1_data.md

@@ -0,0 +1,58 @@
+---
+subcategory: "core/v1"
+page_title: "Kubernetes: kubernetes_secret_v1_data"
+description: |-
+  This resource allows Terraform to manage the data for a Secret that already exists.
+---
+
+# kubernetes_secret_v1_data
+
+This resource allows Terraform to manage data within a pre-existing Secret. This resource uses [field management](https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management) and [server-side apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) to manage only the data that is defined in the Terraform configuration. Existing data not specified in the configuration will be ignored. If data specified in the config is already managed by another client, it will cause a conflict which can be overridden by setting `force` to true.
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `data` (Map of String) The data we want to add to the Secret.
+- `metadata` (Block List, Min: 1, Max: 1) (see [below for nested schema](#nestedblock--metadata))
+
+### Optional
+
+- `field_manager` (String) Set the name of the field manager for the specified labels.
+- `force` (Boolean) Force overwriting data that is managed outside of Terraform.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--metadata"></a>
+### Nested Schema for `metadata`
+
+Required:
+
+- `name` (String) The name of the Secret.
+
+Optional:
+
+- `namespace` (String) The namespace of the Secret.
+
+## Example Usage
+
+```terraform
+resource "kubernetes_secret_v1_data" "example" {
+  metadata {
+    name = "my-secret"
+  }
+  data = {
+    "username" = "admin"
+    "password" = "s3cr3t"
+  }
+}
+```
+
+## Import
+
+This resource does not support the `import` command. As this resource operates on Kubernetes resources that already exist, creating the resource is equivalent to importing it.
+
+