You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# generated by https://github.com/hashicorp/terraform-plugin-docs
3
+
page_title: "k8s_about_k8s_io_cluster_property_v1alpha1 Data Source - terraform-provider-k8s"
4
+
subcategory: "about.k8s.io"
5
+
description: |-
6
+
ClusterProperty is a resource provides a way to store identification related, cluster scoped information for multi-cluster tools while creating flexibility for implementations.
ClusterProperty is a resource provides a way to store identification related, cluster scoped information for multi-cluster tools while creating flexibility for implementations.
12
+
13
+
## Example Usage
14
+
15
+
```terraform
16
+
data "k8s_about_k8s_io_cluster_property_v1alpha1" "example" {
17
+
metadata = {
18
+
name = "some-name"
19
+
20
+
}
21
+
}
22
+
```
23
+
24
+
<!-- schema generated by tfplugindocs -->
25
+
## Schema
26
+
27
+
### Required
28
+
29
+
-`metadata` (Attributes) Data that helps uniquely identify this object. See https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#metadata for more details. (see [below for nested schema](#nestedatt--metadata))
30
+
31
+
### Read-Only
32
+
33
+
-`api_version` (String) The API group of the requested resource.
34
+
-`id` (String) Contains the value `metadata.name`.
35
+
-`kind` (String) The type of the requested resource.
36
+
-`spec` (Attributes) Spec represents the desired behavior. (see [below for nested schema](#nestedatt--spec))
37
+
38
+
<aid="nestedatt--metadata"></a>
39
+
### Nested Schema for `metadata`
40
+
41
+
Required:
42
+
43
+
-`name` (String) Unique identifier for this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names for more details.
44
+
45
+
Read-Only:
46
+
47
+
-`annotations` (Map of String) Keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ for more details.
48
+
-`labels` (Map of String) Keys and values that can be used to organize and categorize objects. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more details.
49
+
50
+
51
+
<aid="nestedatt--spec"></a>
52
+
### Nested Schema for `spec`
53
+
54
+
Read-Only:
55
+
56
+
-`value` (String) Value is the property-dependent string.
# generated by https://github.com/hashicorp/terraform-plugin-docs
3
+
page_title: "k8s_about_k8s_io_cluster_property_v1alpha1_manifest Data Source - terraform-provider-k8s"
4
+
subcategory: "about.k8s.io"
5
+
description: |-
6
+
ClusterProperty is a resource provides a way to store identification related, cluster scoped information for multi-cluster tools while creating flexibility for implementations.
ClusterProperty is a resource provides a way to store identification related, cluster scoped information for multi-cluster tools while creating flexibility for implementations.
12
+
13
+
## Example Usage
14
+
15
+
```terraform
16
+
data "k8s_about_k8s_io_cluster_property_v1alpha1_manifest" "example" {
17
+
metadata = {
18
+
name = "some-name"
19
+
20
+
}
21
+
}
22
+
```
23
+
24
+
<!-- schema generated by tfplugindocs -->
25
+
## Schema
26
+
27
+
### Required
28
+
29
+
-`metadata` (Attributes) Data that helps uniquely identify this object. See https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#metadata for more details. (see [below for nested schema](#nestedatt--metadata))
30
+
-`spec` (Attributes) Spec represents the desired behavior. (see [below for nested schema](#nestedatt--spec))
31
+
32
+
### Read-Only
33
+
34
+
-`id` (String) Contains the value `metadata.name`.
35
+
-`yaml` (String) The generated manifest in YAML format.
36
+
37
+
<aid="nestedatt--metadata"></a>
38
+
### Nested Schema for `metadata`
39
+
40
+
Required:
41
+
42
+
-`name` (String) Unique identifier for this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names for more details.
43
+
44
+
Optional:
45
+
46
+
-`annotations` (Map of String) Keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ for more details.
47
+
-`labels` (Map of String) Keys and values that can be used to organize and categorize objects. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more details.
48
+
49
+
50
+
<aid="nestedatt--spec"></a>
51
+
### Nested Schema for `spec`
52
+
53
+
Required:
54
+
55
+
-`value` (String) Value is the property-dependent string.
Copy file name to clipboardExpand all lines: docs/data-sources/acid_zalan_do_operator_configuration_v1.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,8 +30,10 @@ data "k8s_acid_zalan_do_operator_configuration_v1" "example" {
30
30
31
31
### Read-Only
32
32
33
+
-`api_version` (String) The API group of the requested resource.
33
34
-`configuration` (Attributes) (see [below for nested schema](#nestedatt--configuration))
34
35
-`id` (String) Contains the value `metadata.namespace/metadata.name`.
36
+
-`kind` (String) The type of the requested resource.
35
37
36
38
<aid="nestedatt--metadata"></a>
37
39
### Nested Schema for `metadata`
@@ -160,6 +162,7 @@ Read-Only:
160
162
-`node_readiness_label_merge` (String)
161
163
-`oauth_token_secret_name` (String)
162
164
-`pdb_name_format` (String)
165
+
-`persistent_volume_claim_retention_policy` (Attributes) (see [below for nested schema](#nestedatt--configuration--kubernetes--persistent_volume_claim_retention_policy))
Copy file name to clipboardExpand all lines: docs/data-sources/acid_zalan_do_operator_configuration_v1_manifest.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,6 +163,7 @@ Optional:
163
163
-`node_readiness_label_merge` (String)
164
164
-`oauth_token_secret_name` (String)
165
165
-`pdb_name_format` (String)
166
+
-`persistent_volume_claim_retention_policy` (Attributes) (see [below for nested schema](#nestedatt--configuration--kubernetes--persistent_volume_claim_retention_policy))
Copy file name to clipboardExpand all lines: docs/data-sources/acme_cert_manager_io_challenge_v1.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,9 @@ data "k8s_acme_cert_manager_io_challenge_v1" "example" {
31
31
32
32
### Read-Only
33
33
34
+
-`api_version` (String) The API group of the requested resource.
34
35
-`id` (String) Contains the value `metadata.namespace/metadata.name`.
36
+
-`kind` (String) The type of the requested resource.
35
37
-`spec` (Attributes) (see [below for nested schema](#nestedatt--spec))
36
38
37
39
<aid="nestedatt--metadata"></a>
@@ -336,11 +338,11 @@ Read-Only:
336
338
Read-Only:
337
339
338
340
-`group` (String) Group is the group of the referent. When unspecified, 'gateway.networking.k8s.io' is inferred. To set the core API group (such as for a 'Service' kind referent), Group must be explicitly set to '' (empty string). Support: Core
339
-
-`kind` (String) Kind is kind of the referent. Support: Core(Gateway) Support: Implementation-specific (Other Resources)
341
+
-`kind` (String) Kind is kind of the referent. There are two kinds of parent resources with 'Core' support: * Gateway (Gateway conformance profile) * Service (Mesh conformance profile, experimental, ClusterIP Services only) Support for other resources is Implementation-Specific.
340
342
-`name` (String) Name is the name of the referent. Support: Core
341
-
-`namespace` (String) Namespace is the namespace of the referent. When unspecified, this refers to the local namespace of the Route. Note that there are specific rules for ParentRefs which cross namespace boundaries. Cross-namespace references are only valid if they are explicitly allowed by something in the namespace they are referring to. For example: Gateway has the AllowedRoutes field, and ReferenceGrant provides a generic way to enable any other kind of cross-namespace reference. Support: Core
342
-
- `port` (Number) Port is the network port this Route targets. It can be interpreted differently based on the type of parent resource. When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It's not recommended to set 'Port' unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values. Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted. For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Extended <gateway:experimental>
343
-
- `section_name` (String) SectionName is the name of a section within the target resource. In the following resources, SectionName is interpreted as the following: * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. Implementations MAY choose to support attaching Routes to other resources. If that is the case, they MUST clearly document how SectionName is interpreted. When unspecified (empty string), this will reference the entire resource. For the purpose of status, an attachment is considered successful if at least one section in the parent resource accepts it. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Core
343
+
-`namespace` (String) Namespace is the namespace of the referent. When unspecified, this refers to the local namespace of the Route. Note that there are specific rules for ParentRefs which cross namespace boundaries. Cross-namespace references are only valid if they are explicitly allowed by something in the namespace they are referring to. For example: Gateway has the AllowedRoutes field, and ReferenceGrant provides a generic way to enable any other kind of cross-namespace reference. ParentRefs from a Route to a Service in the same namespace are 'producer' routes, which apply default routing rules to inbound connections from any namespace to the Service. ParentRefs from a Route to a Service in a different namespace are 'consumer' routes, and these routing rules are only applied to outbound connections originating from the same namespace as the Route, for which the intended destination of the connections are a Service targeted as a ParentRef of the Route. Support: Core
344
+
- `port` (Number) Port is the network port this Route targets. It can be interpreted differently based on the type of parent resource. When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It's not recommended to set 'Port' unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values. When the parent resource is a Service, this targets a specific port in the Service spec. When both Port (experimental) and SectionName are specified, the name and port of the selected port must match both specified values. Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted. For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Extended <gateway:experimental>
345
+
- `section_name` (String) SectionName is the name of a section within the target resource. In the following resources, SectionName is interpreted as the following: * Gateway: Listener Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. * Service: Port Name. When both Port (experimental) and SectionName are specified, the name and port of the selected listener must match both specified values. Note that attaching Routes to Services as Parents is part of experimental Mesh support and is not supported for any other purpose. Implementations MAY choose to support attaching Routes to other resources. If that is the case, they MUST clearly document how SectionName is interpreted. When unspecified (empty string), this will reference the entire resource. For the purpose of status, an attachment is considered successful if at least one section in the parent resource accepts it. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway. Support: Core
0 commit comments