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
description: VCluster is the Schema for the vclusters API
22
21
properties:
23
22
apiVersion:
24
-
description: 'APIVersion defines the versioned schema of this representation
25
-
of an object. Servers should convert recognized schemas to the latest
26
-
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
23
+
description: |-
24
+
APIVersion defines the versioned schema of this representation of an object.
25
+
Servers should convert recognized schemas to the latest internal value, and
26
+
may reject unrecognized values.
27
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
27
28
type: string
28
29
kind:
29
-
description: 'Kind is a string value representing the REST resource this
30
-
object represents. Servers may infer this from the endpoint the client
31
-
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
30
+
description: |-
31
+
Kind is a string value representing the REST resource this object represents.
32
+
Servers may infer this from the endpoint the client submits requests to.
33
+
Cannot be updated.
34
+
In CamelCase.
35
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
32
36
type: string
33
37
metadata:
34
38
type: object
@@ -51,8 +55,9 @@ spec:
51
55
- port
52
56
type: object
53
57
helmRelease:
54
-
description: The helm release configuration for the virtual cluster.
55
-
This is optional, but when filled, specified chart will be deployed.
58
+
description: |-
59
+
The helm release configuration for the virtual cluster. This is optional, but
60
+
when filled, specified chart will be deployed.
56
61
properties:
57
62
chart:
58
63
description: infos about what chart to deploy
@@ -72,9 +77,10 @@ spec:
72
77
type: string
73
78
type: object
74
79
kubernetesVersion:
75
-
description: Kubernetes version that should be used in this vcluster
76
-
instance, e.g. "1.23". Versions out of the supported range will
77
-
be ignored, and earliest/latest supported version will be used instead.
80
+
description: |-
81
+
Kubernetes version that should be used in this vcluster instance, e.g. "1.23".
82
+
Versions out of the supported range will be ignored, and earliest/latest supported
83
+
version will be used instead.
78
84
type: string
79
85
type: object
80
86
status:
@@ -88,36 +94,37 @@ spec:
88
94
operational state.
89
95
properties:
90
96
lastTransitionTime:
91
-
description: Last time the condition transitioned from one status
92
-
to another. This should be when the underlying condition changed.
93
-
If that is not known, then using the time when the API field
94
-
changed is acceptable.
97
+
description: |-
98
+
Last time the condition transitioned from one status to another.
99
+
This should be when the underlying condition changed. If that is not known, then using the time when
100
+
the API field changed is acceptable.
95
101
format: date-time
96
102
type: string
97
103
message:
98
-
description: A human readable message indicating details about
99
-
the transition. This field may be empty.
104
+
description: |-
105
+
A human readable message indicating details about the transition.
106
+
This field may be empty.
100
107
type: string
101
108
reason:
102
-
description: The reason for the condition's last transition
103
-
in CamelCase. The specific API may choose whether this field
104
-
is considered a guaranteed API. This field may not be empty.
109
+
description: |-
110
+
The reason for the condition's last transition in CamelCase.
111
+
The specific API may choose whether this field is considered a guaranteed API.
112
+
This field may not be empty.
105
113
type: string
106
114
severity:
107
-
description: Severity provides an explicit classification of
108
-
Reason code, so the users or machines can immediately understand
109
-
the current situation and act accordingly. The Severity field
110
-
MUST be set only when Status=False.
115
+
description: |-
116
+
Severity provides an explicit classification of Reason code, so the users or machines can immediately
117
+
understand the current situation and act accordingly.
118
+
The Severity field MUST be set only when Status=False.
111
119
type: string
112
120
status:
113
121
description: Status of the condition, one of True, False, Unknown.
114
122
type: string
115
123
type:
116
-
description: Type of condition in CamelCase or in foo.example.com/CamelCase.
117
-
Many .condition.type values are consistent across resources
118
-
like Available, but because arbitrary conditions can be useful
119
-
(see .node.status.conditions), the ability to deconflict is
120
-
important.
124
+
description: |-
125
+
Type of condition in CamelCase or in foo.example.com/CamelCase.
126
+
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions
127
+
can be useful (see .node.status.conditions), the ability to deconflict is important.
121
128
type: string
122
129
required:
123
130
- status
@@ -129,8 +136,9 @@ spec:
129
136
was initialized.
130
137
type: boolean
131
138
message:
132
-
description: Message describes the reason in human readable form why
133
-
the cluster is in the currrent phase
139
+
description: |-
140
+
Message describes the reason in human readable form why the cluster is in the currrent
141
+
phase
134
142
type: string
135
143
observedGeneration:
136
144
description: ObservedGeneration is the latest generation observed
@@ -146,18 +154,13 @@ spec:
146
154
ready.
147
155
type: boolean
148
156
reason:
149
-
description: Reason describes the reason in machine readable form
150
-
why the cluster is in the current phase
157
+
description: |-
158
+
Reason describes the reason in machine readable form why the cluster is in the current
0 commit comments