Initialize a new cluster
Requirements
Section titled “Requirements”Before your first implementation, make sure to be able to setup all the required properties available in the configuration reference.
Configuration file
Section titled “Configuration file”Creating a config.yaml file is required in order to make your first cluster bootstrap.
This file will contain all the needed informations and parameters for the desired cloud provider and the final cluster configuration.
Initialization
Section titled “Initialization”Use the previously created configuration file and provide it to K8SaaS using the --init-config CLI parameter.
k8saas init --init-config config.yamlAvailable flags
Section titled “Available flags”user@machine:~/k8saas$ k8saas init -hInitialize k8saas cluster.
Usage: k8saas init [flags]
Flags: --baremetal-controlplane-availability-timeout int Baremetal controlplane availability timeout in seconds (default 5400) --baremetal-creation-timeout int Baremetal installation creation timeout in seconds (default 600) --baremetal-host-availability-timeout int Baremetal host availability timeout in seconds (default 900) --base-dir string base directory of k8saas & configuration files (default ".") --cluster-creation-timeout int Cluster creation timeout in seconds (default 300) --gcp-key-file string path to gcp service account authentication file (in json format) -h, --help help for init --init-config string cluster initialization config file (in yaml format) --resource-creation-timeout int General resource creation timeout in seconds (default 1500) --ssh-public-key-path string path to your ssh public key, used by few providers
Global Flags: --config string cli config file (default is $HOME/.k8saas.yaml) -v, --verbose count verbose output (repeat for more verbosity)