yurtadm_init
yurtadm init
Run this command in order to set up the OpenYurt control plane
yurtadm init [flags]
Options
--apiserver-advertise-address string The IP address the API Server will advertise it's listening on.
-h, --help help for init
--image-repository string Choose a registry to pull cluster images from (default "registry.cn-hangzhou.aliyuncs.com/openyurt")
--openyurt-version string Choose a specific OpenYurt version for the control plane. (default "latest")
--pod-network-cidr string Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
--service-cidr string Use alternative range of IP address for service VIPs.
--yurt-tunnel-server-address string The yurt-tunnel-server address.
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
--kubeconfig string The path to the kubeconfig file
--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
--log_file string If non-empty, use this log file
--log_file_max_size uint Defines the maximum size a log file can grow to. 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)
--skip_headers If true, avoid header prefixes in the log messages
--skip_log_headers If true, avoid headers when opening log files
--stderrthreshold severity logs at or above this threshold go to stderr (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
- yurtadm - yurtadm administers the yurt cluster