Skip to main content

furyctl get upgrade-paths

Get available upgrade paths for the kind and version defined in the configuration file or a custom one.

Synopsis​

Get available upgrade paths for the kind and version defined in the configuration file or a custom one. If the "--from" or "--kind" parameters are specified, the command will give the upgrade path for those instead.

Usage​

furyctl get upgrade-paths [flags]

Examples​

  furyctl get upgrade-paths                                 shows the available upgrade paths for the kind and distribution version defined in the configuration file (furyctl.yaml by default)
  furyctl get upgrade-paths --from vX.Y.Z                   shows the available upgrade paths for the kind defined in the configuration file but for the version X.Y.Z instead.
  furyctl get upgrade-paths --kind OnPremises               shows the available upgrade paths for the version defined in the configuration file but for the OnPremises kind, even if the cluster is an EKSCluster, for example.
  furyctl get upgrade-paths --kind OnPremises --from X.Y.X  shows the available upgrade paths for the version X.Y.Z of the OnPremises kind, without reading the configuration file.

Options​

  -b, --bin-path string          Path to the folder where all the dependencies' binaries are installed
  -c, --config string            Path to the configuration file (default "furyctl.yaml")
      --distro-location string   Location where to download schemas, defaults and the distribution manifests from. It can either be a local path (eg: /path/to/distribution) or a remote URL (eg: git::git@github.com:sighupio/distribution?depth=1&ref=BRANCH_NAME). Any format supported by hashicorp/go-getter can be used
      --from string              Show upgrade paths for the version specified (eg. 1.29.2) instead of the distribution version in the configuration file
  -h, --help                     help for upgrade-paths
  -k, --kind string              Show upgrade paths for the kind of cluster specified instead of the kind defined in the configuration file. Options are: EKSCluster, KFDDistribution, OnPremises
      --skip-deps-download       Skip downloading the binaries
      --skip-deps-validation     Skip validating dependencies

Options inherited from parent commands​

  -D, --debug                       Enables furyctl debug output. This will greatly increase the verbosity. Debug logs and additional logs are also always written to the log file. See the --log flag.
  -d, --disable-analytics           Disable analytics
  -g, --git-protocol git-protocol   Download repositories using the given protocol. Use when SSH traffic is being blocked or when SSH client has not been configured
                                    set the GITHUB_TOKEN environment variable with your token to use authentication while downloading, for example for private repositories. 
                                    Options are: ssh, https (default https)
  -H, --https                       DEPRECATED: by default furyctl uses https protocol to download repositories. See --git-protocol flag (default true)
  -l, --log string                  Path to a file or folder where to write logs to. Set to 'stdout' write to standard output. Target path will be created if it does not exists. Path is relative to --workdir. Default is '<outdir>/.furyctl/furyctl.<timestamp>-<random number>.log'
  -T, --no-tty                      Disable TTY making furyctl's output more friendly to non-interactive shells by disabling animations and colors
  -o, --outdir string               Path where to create the ".furyctl" data directory. Default is the user's home. Path is relative to --workdir
  -w, --workdir string              Switch to a different working directory before executing the given subcommand. NOTE: this will affect all the paths passed, including other flags like outdir and log, for example

See Also​

  • furyctl get - Get the kubeconfig, available upgrade paths for a cluster or compatible versions to use between SD, providers, furyctl