karmadactl join
Register a cluster to Karmada control plane with Push mode
Synopsis
Register a cluster to Karmada control plane with Push mode.
karmadactl join CLUSTER_NAME --cluster-kubeconfig=<KUBECONFIG>
Examples
# Join cluster into karmada control plane, if '--cluster-context' not specified, take the cluster name as the context
karmadactl join CLUSTER_NAME --cluster-kubeconfig=<KUBECONFIG>
Options
--cluster-context string Name of cluster context in kubeconfig. The current context is used by default.
--cluster-kubeconfig string Path of the cluster's kubeconfig.
--cluster-namespace string Namespace in the control plane where member cluster secrets are stored. (default "karmada-cluster")
--cluster-provider string Provider of the joining cluster. The Karmada scheduler can use this information to spread workloads across providers for higher availability.
--cluster-region string The region of the joining cluster. The Karmada scheduler can use this information to spread workloads across regions for higher availability.
--cluster-zones strings The zones of the joining cluster. The Karmada scheduler can use this information to spread workloads across zones for higher availability.
--dry-run Run the command in dry-run mode, without making any server requests.
-h, --help help for join
--karmada-as string Username to impersonate for the operation in karmada control plane. User could be a regular user or a service account in a namespace.
--karmada-as-group stringArray Group to impersonate for the operation in karmada control plane, this flag can be repeated to specify multiple groups.
--karmada-as-uid string UID to impersonate for the operation in karmada control plane.
--karmada-context string The name of the kubeconfig context to use
--kubeconfig string Path to the kubeconfig file to use for CLI requests.
Options inherited from parent commands
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
--log-file string If non-empty, use this log file (no effect when -logtostderr=true)
--log-file-max-size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
--logtostderr log to standard error instead of files (default true)
--one-output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
--skip-headers If true, avoid header prefixes in the log messages
--skip-log-headers If true, avoid headers when opening log files (no effect when -logtostderr=true)
--stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)
-v, --v Level number for the log level verbosity
--vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
SEE ALSO
- karmadactl - karmadactl controls a Kubernetes Cluster Federation.