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
{{ message }}
This repository was archived by the owner on Nov 20, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: config/crd/bases/infrastructure.crit.sh_dockerinfrastructureproviders.yaml
+5-12Lines changed: 5 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -29,33 +29,26 @@ spec:
29
29
status: {}
30
30
validation:
31
31
openAPIV3Schema:
32
-
description: DockerInfrastructureProvider is the Schema for the infrastructureproviders
33
-
API
32
+
description: DockerInfrastructureProvider is the Schema for the infrastructureproviders API
34
33
properties:
35
34
apiVersion:
36
-
description: 'APIVersion defines the versioned schema of this representation
37
-
of an object. Servers should convert recognized schemas to the latest
38
-
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
35
+
description: 'APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
39
36
type: string
40
37
kind:
41
-
description: 'Kind is a string value representing the REST resource this
42
-
object represents. Servers may infer this from the endpoint the client
43
-
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
38
+
description: 'Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
44
39
type: string
45
40
metadata:
46
41
type: object
47
42
spec:
48
-
description: DockerInfrastructureProviderSpec defines the desired state
49
-
of DockerInfrastructureProvider
43
+
description: DockerInfrastructureProviderSpec defines the desired state of DockerInfrastructureProvider
50
44
properties:
51
45
defaultImage:
52
46
type: string
53
47
required:
54
48
- defaultImage
55
49
type: object
56
50
status:
57
-
description: InfrastructureProviderStatus defines the observed state of
58
-
DockerInfrastructureProvider
51
+
description: InfrastructureProviderStatus defines the observed state of DockerInfrastructureProvider
Copy file name to clipboardExpand all lines: config/crd/bases/infrastructure.crit.sh_dockermachines.yaml
+20-32Lines changed: 20 additions & 32 deletions
Original file line number
Diff line number
Diff line change
@@ -24,14 +24,10 @@ spec:
24
24
description: DockerMachine is the Schema for the dockermachines API
25
25
properties:
26
26
apiVersion:
27
-
description: 'APIVersion defines the versioned schema of this representation
28
-
of an object. Servers should convert recognized schemas to the latest
29
-
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
27
+
description: 'APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
30
28
type: string
31
29
kind:
32
-
description: 'Kind is a string value representing the REST resource this
33
-
object represents. Servers may infer this from the endpoint the client
34
-
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: 'Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
35
31
type: string
36
32
metadata:
37
33
type: object
@@ -54,35 +50,27 @@ spec:
54
50
status:
55
51
description: DockerMachineStatus defines the observed state of DockerMachine
56
52
properties:
53
+
addresses:
54
+
description: Addresses contains the docker container associated addresses.
55
+
items:
56
+
description: MachineAddress contains information for the node's address.
57
+
properties:
58
+
address:
59
+
description: The machine address.
60
+
type: string
61
+
type:
62
+
description: Machine address type, one of Hostname, ExternalIP or InternalIP.
63
+
type: string
64
+
required:
65
+
- address
66
+
- type
67
+
type: object
68
+
type: array
57
69
failureMessage:
58
-
description: "FailureMessage will be set in the event that there is
59
-
a terminal problem reconciling the Machine and will contain a more
60
-
verbose string suitable for logging and human consumption. \n This
61
-
field should not be set for transitive errors that a controller faces
62
-
that are expected to be fixed automatically over time (like service
63
-
outages), but instead indicate that something is fundamentally wrong
64
-
with the Machine's spec or the configuration of the controller, and
65
-
that manual intervention is required. Examples of terminal errors
66
-
would be invalid combinations of settings in the spec, values that
67
-
are unsupported by the controller, or the responsible controller itself
68
-
being critically misconfigured. \n Any transient errors that occur
69
-
during the reconciliation of Machines can be added as events to the
70
-
Machine object and/or logged in the controller's output."
70
+
description: "FailureMessage will be set in the event that there is a terminal problem reconciling the Machine and will contain a more verbose string suitable for logging and human consumption. \n This field should not be set for transitive errors that a controller faces that are expected to be fixed automatically over time (like service outages), but instead indicate that something is fundamentally wrong with the Machine's spec or the configuration of the controller, and that manual intervention is required. Examples of terminal errors would be invalid combinations of settings in the spec, values that are unsupported by the controller, or the responsible controller itself being critically misconfigured. \n Any transient errors that occur during the reconciliation of Machines can be added as events to the Machine object and/or logged in the controller's output."
71
71
type: string
72
72
failureReason:
73
-
description: "FailureReason will be set in the event that there is a
74
-
terminal problem reconciling the Machine and will contain a succinct
75
-
value suitable for machine interpretation. \n This field should not
76
-
be set for transitive errors that a controller faces that are expected
77
-
to be fixed automatically over time (like service outages), but instead
78
-
indicate that something is fundamentally wrong with the Machine's
79
-
spec or the configuration of the controller, and that manual intervention
80
-
is required. Examples of terminal errors would be invalid combinations
81
-
of settings in the spec, values that are unsupported by the controller,
82
-
or the responsible controller itself being critically misconfigured.
83
-
\n Any transient errors that occur during the reconciliation of Machines
84
-
can be added as events to the Machine object and/or logged in the
85
-
controller's output."
73
+
description: "FailureReason will be set in the event that there is a terminal problem reconciling the Machine and will contain a succinct value suitable for machine interpretation. \n This field should not be set for transitive errors that a controller faces that are expected to be fixed automatically over time (like service outages), but instead indicate that something is fundamentally wrong with the Machine's spec or the configuration of the controller, and that manual intervention is required. Examples of terminal errors would be invalid combinations of settings in the spec, values that are unsupported by the controller, or the responsible controller itself being critically misconfigured. \n Any transient errors that occur during the reconciliation of Machines can be added as events to the Machine object and/or logged in the controller's output."
0 commit comments