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
Copy file name to clipboardexpand all lines: operator/v1/0000_00_operator.open-cluster-management.io_klusterlets.crd.yaml
+36
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,42 @@ spec:
41
41
required:
42
42
- mode
43
43
properties:
44
+
detached:
45
+
description: Detached includes configurations we needs for clustermanager in the detached mode.
46
+
type: object
47
+
properties:
48
+
registrationWebhookConfiguration:
49
+
description: RegistrationWebhookConfiguration represents the customized webhook-server configuration of registration.
50
+
type: object
51
+
required:
52
+
- address
53
+
properties:
54
+
address:
55
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
60
+
type: integer
61
+
format: int32
62
+
default: 443
63
+
maximum: 65535
64
+
workWebhookConfiguration:
65
+
description: WorkWebhookConfiguration represents the customized webhook-server configuration of work.
66
+
type: object
67
+
required:
68
+
- address
69
+
properties:
70
+
address:
71
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
76
+
type: integer
77
+
format: int32
78
+
default: 443
79
+
maximum: 65535
44
80
mode:
45
81
description: "Mode can be Default or Detached. For cluster-manager: - In Default mode, the Hub is installed as a whole and all parts of Hub are deployed in the same cluster. - In Detached mode, only crd and configurations are installed on one cluster(defined as hub-cluster). Controllers run in another cluster (defined as management-cluster) and connect to the hub with the kubeconfig in secret of \"external-hub-kubeconfig\"(a kubeconfig of hub-cluster with cluster-admin permission). For klusterlet: - In Default mode, all klusterlet related resources are deployed on the managed cluster. - In Detached mode, only crd and configurations are installed on the spoke/managed cluster. Controllers run in another cluster (defined as management-cluster) and connect to the mangaged cluster with the kubeconfig in secret of \"external-managed-kubeconfig\"(a kubeconfig of managed-cluster with cluster-admin permission). The purpose of Detached mode is to give it more flexibility, for example we can install a hub on a cluster with no worker nodes, meanwhile running all deployments on another more powerful cluster. And we can also register a managed cluster to the hub that has some firewall rules preventing access from the managed cluster. \n Note: Do not modify the Mode field once it's applied."
Copy file name to clipboardexpand all lines: operator/v1/0000_01_operator.open-cluster-management.io_clustermanagers.crd.yaml
+36-38
Original file line number
Diff line number
Diff line change
@@ -33,54 +33,52 @@ spec:
33
33
deployOption:
34
34
description: DeployOption contains the options of deploying a cluster-manager Default mode is used if DeployOption is not set.
35
35
type: object
36
-
default:
37
-
mode: Default
38
36
required:
39
37
- mode
40
38
properties:
39
+
detached:
40
+
description: Detached includes configurations we needs for clustermanager in the detached mode.
41
+
type: object
42
+
properties:
43
+
registrationWebhookConfiguration:
44
+
description: RegistrationWebhookConfiguration represents the customized webhook-server configuration of registration.
45
+
type: object
46
+
required:
47
+
- address
48
+
properties:
49
+
address:
50
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
55
+
type: integer
56
+
format: int32
57
+
default: 443
58
+
maximum: 65535
59
+
workWebhookConfiguration:
60
+
description: WorkWebhookConfiguration represents the customized webhook-server configuration of work.
61
+
type: object
62
+
required:
63
+
- address
64
+
properties:
65
+
address:
66
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
71
+
type: integer
72
+
format: int32
73
+
default: 443
74
+
maximum: 65535
41
75
mode:
42
76
description: "Mode can be Default or Detached. For cluster-manager: - In Default mode, the Hub is installed as a whole and all parts of Hub are deployed in the same cluster. - In Detached mode, only crd and configurations are installed on one cluster(defined as hub-cluster). Controllers run in another cluster (defined as management-cluster) and connect to the hub with the kubeconfig in secret of \"external-hub-kubeconfig\"(a kubeconfig of hub-cluster with cluster-admin permission). For klusterlet: - In Default mode, all klusterlet related resources are deployed on the managed cluster. - In Detached mode, only crd and configurations are installed on the spoke/managed cluster. Controllers run in another cluster (defined as management-cluster) and connect to the mangaged cluster with the kubeconfig in secret of \"external-managed-kubeconfig\"(a kubeconfig of managed-cluster with cluster-admin permission). The purpose of Detached mode is to give it more flexibility, for example we can install a hub on a cluster with no worker nodes, meanwhile running all deployments on another more powerful cluster. And we can also register a managed cluster to the hub that has some firewall rules preventing access from the managed cluster. \n Note: Do not modify the Mode field once it's applied."
43
77
type: string
44
78
default: Default
45
79
enum:
46
80
- Default
47
81
- Detached
48
-
detached:
49
-
description: Detached includes configurations we needs for clustermanager in the detached mode.
50
-
type: object
51
-
properties:
52
-
registrationWebhookConfiguration:
53
-
description: RegistrationWebhookConfiguration represents the customized webhook-server configuration of registration.
54
-
type: object
55
-
required:
56
-
- address
57
-
properties:
58
-
address:
59
-
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
64
-
type: integer
65
-
format: int32
66
-
default: 443
67
-
maximum: 65535
68
-
workWebhookConfiguration:
69
-
description: WorkWebhookConfiguration represents the customized webhook-server configuration of work.
70
-
type: object
71
-
required:
72
-
- address
73
-
properties:
74
-
address:
75
-
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
Copy file name to clipboardexpand all lines: operator/v1/0001_00_operator.open-cluster-management.io_klusterlets.crd.yaml
+36
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,42 @@ spec:
41
41
required:
42
42
- mode
43
43
properties:
44
+
detached:
45
+
description: Detached includes configurations we needs for clustermanager in the detached mode.
46
+
type: object
47
+
properties:
48
+
registrationWebhookConfiguration:
49
+
description: RegistrationWebhookConfiguration represents the customized webhook-server configuration of registration.
50
+
type: object
51
+
required:
52
+
- address
53
+
properties:
54
+
address:
55
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
60
+
type: integer
61
+
format: int32
62
+
default: 443
63
+
maximum: 65535
64
+
workWebhookConfiguration:
65
+
description: WorkWebhookConfiguration represents the customized webhook-server configuration of work.
66
+
type: object
67
+
required:
68
+
- address
69
+
properties:
70
+
address:
71
+
description: Address represents the address of a webhook-server. It could be in IP format or fqdn format. The Address must be reachable by apiserver of the hub cluster.
description: Port represents the port of a webhook-server. The default value of Port is 443.
76
+
type: integer
77
+
format: int32
78
+
default: 443
79
+
maximum: 65535
44
80
mode:
45
81
description: "Mode can be Default or Detached. For cluster-manager: - In Default mode, the Hub is installed as a whole and all parts of Hub are deployed in the same cluster. - In Detached mode, only crd and configurations are installed on one cluster(defined as hub-cluster). Controllers run in another cluster (defined as management-cluster) and connect to the hub with the kubeconfig in secret of \"external-hub-kubeconfig\"(a kubeconfig of hub-cluster with cluster-admin permission). For klusterlet: - In Default mode, all klusterlet related resources are deployed on the managed cluster. - In Detached mode, only crd and configurations are installed on the spoke/managed cluster. Controllers run in another cluster (defined as management-cluster) and connect to the mangaged cluster with the kubeconfig in secret of \"external-managed-kubeconfig\"(a kubeconfig of managed-cluster with cluster-admin permission). The purpose of Detached mode is to give it more flexibility, for example we can install a hub on a cluster with no worker nodes, meanwhile running all deployments on another more powerful cluster. And we can also register a managed cluster to the hub that has some firewall rules preventing access from the managed cluster. \n Note: Do not modify the Mode field once it's applied."
0 commit comments