Skip to content

mkectl apply

mkectl apply#

Apply a configuration to a cluster

mkectl apply [flags]

Options#

      --admin-password string            Password for the default admin user
      --bpf-dns-patch                    Patch DNS for tigera-operator in BPF mode to make EC2 DNS work in tigera-operator pods
      --cni-check-port int32             Use specified port number for verifying networking availability post CNI install (default 80)
      --cni-check-timeout int            Use specified timeout(in minutes) around verifying networking availability post CNI install (default 15)
      --cni-check-timeout-windows int    Use specified timeout(in minutes) around verifying Windows networking (node CNI readiness, pod DNS, pod connectivity); only applied when the cluster has Windows hosts (default 25)
      --collect-facts-timeout duration   Timeout for the collect-facts phase (gathering per-host facts such as cgroup version over SSH) (default 5m0s)
      --concurrency int                  Maximum number of nodes to configure in parallel, set to 0 for unlimited (default 30)
      --dry-run                          Simulate the apply process without making any changes
      --feature-gates string             MKE operator feature gates list, formatted formatted as "key1=value1,key2=value2,..."
      --force                            Bypass user confirmations. This will apply changes without any confirmations
  -h, --help                             help for apply
      --lease-adopt-stale                if true, matching stale lease would be adopted instead of failing with error
      --lease-renew-interval duration    lease renew interval for cluster-wide/node operations, should be < leaseTTL (default 20s)
      --lease-ttl duration               lease TTL for cluster-wide/node operations (default 1m0s)
      --skip-addon-wait                  Do not wait for MKE addons to become deployed
      --skip-cni-check                   Do not verify that networking is available
      --skip-image-presence-check        Skip the image presence in registry check in airgap mode
      --skip-os-check                    Skip the supported-OS-variant check. Use when nodes are running an OS patch level not yet on the supported list. The compatibility matrix in the docs remains the source of truth for officially supported variants.
      --skip-storage-check               Skip storage checks
      --skip-wait-k8s-ready-check        Skip waiting for k8s API reachable after creating/modifying cluster with k0sctl
      --support-dump-no-sudo             Use support dump commands without sudo for collecting support dump for the cluster
      --support-dump-timeout int         Use specified timeout(in minutes) around collecting support dump for the cluster (default 20)
      --timeout-minutes int              Use specified timeout(in minutes) around the entirety of apply/install (default 60)

Options inherited from parent commands#

  -f, --file string              path to the config file. Not needed for restore where config is loaded from the backup (default "mke4.yaml")
      --kubeconfig string        path to the kubeconfig file of the existing or restored cluster. DO NOT USE when creating a new cluster (default "/home/runner/.mke/mke.kubeconf")
  -l, --logLevel string          specify a log level (info, warn, debug, trace, error) (default "info")
      --no-color                 when provided, disables colored output
      --no-pretty-print          when provided, disables pretty print output formatting
      --version version[=true]   --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version