This version is under construction, please use an official release version

GitHub Workflow description

Automated pipeline was created in GitHub or GitLab to automate all installation steps to have KKP up and running and ready to operate with GitOps (using Flux tool).

Pipeline Schema

Jobs are being triggered on 2 specific events - either on your Pull (Merge) Requests or after push to main branch. On pull requests, only the jobs for terraform validate and plan are executed (so that you have visibility what is going to change). All other jobs are being executed on the main branch after push (in case that any files in directories kubeone, kubermatic, terraform or .github/workflows have changed).

Jobs

terraform-kkp-validate, terraform-kkp-dns-validate

Runs validation of all Terraform modules.

terraform-backend-prepare

Prepares Terraform backend for storing Terraform state.

==> This is performed only with GitHub and AWS, if you are using GitLab, terraform state is stored in GitLab directly.

terraform-plan

Prepares Terraform plan based on the stored Terraform state.

terraform-apply

Applies the Terraform changes based on a Terraform state.

==> VM instances, LB for Kubernetes and other resources are prepared at this stage

Runs only after the push in main branch.

kubeone-apply

Performs the cluster provisioning using the kubeone tool.

==> Kubernetes cluster is ready to use at this stage

Runs only after the push in main branch.

kkp-deploy

Performs the Kubermatic Kubernetes Platform installation with installer.

==> KKP platform with core components is prepared at this stage

Runs only after the push in main branch.

dns-update

Updates DNS records for KKP services using Terraform module, optional step for AWS only.

==> Services from Kubernetes for KKP are retrieved and external IPs are registered in Route53 using hosted zone

Runs only after the push in main branch.

flux-bootstrap

Initiates Flux v2 using flux bootstrap github command.

==> Monitoring stack for KKP and other KKP resources (seed, preset, project) are delivered after Flux is set up on cluster, Flux itself is also managed by the same GitHub repository

Runs only after the push in main branch.