CI: run tfplugindocs generate to address workflow failure

docs/data-sources/config_map_v1.md

@@ -45,6 +45,7 @@ Read-Only:
 
 
 
+
 ~> **Note:** All arguments including the config map data will be stored in the raw state as plain-text. [Read more about sensitive data in state](/docs/state/sensitive-data.html).
 
 ## Example Usage

docs/data-sources/ingress_v1.md

@@ -119,7 +119,7 @@ Read-Only:
 - `service` (List of Object) (see [below for nested schema](#nestedobjatt--spec--rule--http--path--backend--service))
 
 <a id="nestedobjatt--spec--rule--http--path--backend--resource"></a>
-### Nested Schema for `spec.rule.http.path.backend.resource`
+### Nested Schema for `spec.rule.http.path.backend.service`
 
 Read-Only:
 

docs/data-sources/persistent_volume_v1.md

@@ -143,7 +143,7 @@ Optional:
 - `user` (String) User is the rados user name, default is admin. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it
 
 <a id="nestedblock--spec--persistent_volume_source--ceph_fs--secret_ref"></a>
-### Nested Schema for `spec.persistent_volume_source.ceph_fs.secret_ref`
+### Nested Schema for `spec.persistent_volume_source.ceph_fs.user`
 
 Optional:
 
@@ -184,7 +184,7 @@ Optional:
 - `volume_attributes` (Map of String) Attributes of the volume to publish.
 
 <a id="nestedblock--spec--persistent_volume_source--csi--controller_expand_secret_ref"></a>
-### Nested Schema for `spec.persistent_volume_source.csi.controller_expand_secret_ref`
+### Nested Schema for `spec.persistent_volume_source.csi.volume_attributes`
 
 Optional:
 
@@ -193,7 +193,7 @@ Optional:
 
 
 <a id="nestedblock--spec--persistent_volume_source--csi--controller_publish_secret_ref"></a>
-### Nested Schema for `spec.persistent_volume_source.csi.controller_publish_secret_ref`
+### Nested Schema for `spec.persistent_volume_source.csi.volume_attributes`
 
 Optional:
 
@@ -202,7 +202,7 @@ Optional:
 
 
 <a id="nestedblock--spec--persistent_volume_source--csi--node_publish_secret_ref"></a>
-### Nested Schema for `spec.persistent_volume_source.csi.node_publish_secret_ref`
+### Nested Schema for `spec.persistent_volume_source.csi.volume_attributes`
 
 Optional:
 
@@ -211,7 +211,7 @@ Optional:
 
 
 <a id="nestedblock--spec--persistent_volume_source--csi--node_stage_secret_ref"></a>
-### Nested Schema for `spec.persistent_volume_source.csi.node_stage_secret_ref`
+### Nested Schema for `spec.persistent_volume_source.csi.volume_attributes`
 
 Optional:
 

docs/guides/alpha-manifest-migration-guide.md → docs/guides/alpha-manifest-migration-guide.markdown

@@ -1,5 +1,5 @@
 ---
-subcategory: ""
+layout: "kubernetes"
 page_title: "Migrating `kubernetes_manifest` resources from the kubernetes-alpha provider"
 description: |-
   This guide covers adopting `kubernetes_manifest` resources created using the kubernetes-alpha provider.

docs/guides/getting-started.html.md → docs/guides/getting-started.html.markdown

@@ -1,5 +1,5 @@
 ---
-subcategory: ""
+layout: "kubernetes"
 page_title: "Kubernetes: Getting Started with Kubernetes provider"
 description: |-
   This guide focuses on configuring authentication to your existing Kubernetes

docs/guides/v2-upgrade-guide.md → docs/guides/v2-upgrade-guide.markdown

@@ -1,5 +1,5 @@
 ---
-subcategory: ""
+layout: "kubernetes"
 page_title: "Kubernetes: Upgrade Guide for Kubernetes Provider v2.0.0"
 description: |-
   This guide covers the changes introduced in v2.0.0 of the Kubernetes provider and what you may need to do to upgrade your configuration.

docs/guides/versioned-resources.md → docs/guides/versioned-resources.markdown

@@ -1,5 +1,5 @@
 ---
-subcategory: ""
+layout: "kubernetes"
 page_title: "Versioned resource names"
 description: |-
   This guide explains the naming conventions for resources and data sources in the Kubernetes provider. 

docs/index.md

@@ -195,9 +195,9 @@ The following arguments are supported:
 * `token` - (Optional) Token of your service account. Can be sourced from `KUBE_TOKEN`.
 * `proxy_url` - (Optional) URL to the proxy to be used for all API requests. URLs with "http", "https", and "socks5" schemes are supported. Can be sourced from `KUBE_PROXY_URL`.
 * `exec` - (Optional) Configuration block to use an [exec-based credential plugin] (https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins), e.g. call an external command to receive user credentials.
-* `api_version` - (Required) API version to use when decoding the ExecCredentials resource, e.g. `client.authentication.k8s.io/v1beta1`.
-* `command` - (Required) Command to execute.
-* `args` - (Optional) List of arguments to pass when executing the plugin.
-* `env` - (Optional) Map of environment variables to set when executing the plugin.
+  * `api_version` - (Required) API version to use when decoding the ExecCredentials resource, e.g. `client.authentication.k8s.io/v1beta1`.
+  * `command` - (Required) Command to execute.
+  * `args` - (Optional) List of arguments to pass when executing the plugin.
+  * `env` - (Optional) Map of environment variables to set when executing the plugin.
 * `ignore_annotations` - (Optional) List of Kubernetes metadata annotations to ignore across all resources handled by this provider for situations where external systems are managing certain resource annotations. This option does not affect annotations within a template block. Each item is a regular expression.
 * `ignore_labels` - (Optional) List of Kubernetes metadata labels to ignore across all resources handled by this provider for situations where external systems are managing certain resource labels. This option does not affect annotations within a template block. Each item is a regular expression.

docs/resources/certificate_signing_request_v1.md

@@ -97,18 +97,18 @@ Custom signerNames can also be specified. The signer defines:
 
 Optional:
 
-- `expiration_seconds` (Integer) expirationSeconds is the requested duration of validity of the issued certificate.
+- `expiration_seconds` (Number) expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.
 
-The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration. The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.
+The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.
 
 Certificate signers may not honor this field for various reasons:
 
-1. Old signer that is unaware of the field (such as the in-tree implementations prior to v1.22)
-2. Signer whose configured maximum is shorter than the requested duration
-3. Signer whose configured minimum is longer than the requested duration
+  1. Old signer that is unaware of the field (such as the in-tree
+     implementations prior to v1.22)
+  2. Signer whose configured maximum is shorter than the requested duration
+  3. Signer whose configured minimum is longer than the requested duration
 
 The minimum valid value for expirationSeconds is 600, i.e. 10 minutes.
-
 - `usages` (Set of String) usages specifies a set of key usages requested in the issued certificate.
 
 Requests for TLS client certificates typically request: "digital signature", "key encipherment", "client auth".