Skip to main content
Version: 2.10

Vultr Cloud

Summary​

Kubefirst and Kubefirst Pro support provisioning in Vultr with two main installation methods, through the Kubefirst CLI, and through our UI.

In this section of our documentation you can find content specific to our Vultr support and using Kubefirst.

Vultr Supported Installs​

Kubefirst can be installed with Vultr in two ways:

  • Through the Kubefirst CLI with MacOS, Linux, or Windows (using WSL and Ubuntu)
  • With Vultr and the Kubefirst UI.
    • One option uses a Kubefirst command Recommended for users who do not have an existing cluster
    • The second option uses Helm and is Recommended for users with an existing cluster for install

Regardless of the installation method, the functionality remains the same for Kubefirst and Kubefirst Pro, and any features including cluster creation and management are consistent across clouds.

Installation Components​

The Vultr install and provisioning process creates the following:

  • a Kubernetes management cluster in the Vultr cloud.
  • a Git repository (gitops) from our gitops-template in your selected Git provider
  • an Argo CD installation bootstrapped to the gitops repository to power the Kubefirst platform
  • all the platform applications using GitOps (from the /registry folder in the gitops repository)
  • a Terraform configuration for Vault (from the /terraform/vault folder in the gitops repository)
  • a Terraform configuration for the gitops repository to automatically run Terraform executions through Atlantis
  • an Argo Workflows integration with your selected Git provider
  • an Argo Workflows cluster workflow templates to build containers, publish Helm charts, and provide a GitOps delivery pipeline
  • a metaphor installation for our sample application that has built-in automation to demonstrate app delivery
  • Access to the Kubefirst UI if desired, while you can opt-out of this functionality access to the Kubefirst UI and Kubefirst Pro are free for your management cluster