cluster-api-provider-hcloud

cluster-api-provider-hcloud

Cluster API infrastructure provider for Hetzner Cloud https://hetzner.cloud

Docs

https://docs.capihc.com/ or under ./docs/src

Quick start

At the moment please use the Developer Guide below.

More information available in the Cluster API - Quick Start guide

• Make sure you have a Kubernetes management cluster available and your KUBECONFIG and context set correctly

• Ensure you have a recent clusterctl release (tested with v0.3.9)

• Ensure your Hcloud API token is created as secret in the kubernetes API:

kubectl create secret generic hcloud-token --from-literal=token=$TOKEN

• Register this infrastructure provider in your $HOME/.cluster-api/clusterctl.yaml:

providers:
  - name: "hcloud"
    url: "https://github.com/cluster-api-provider-hcloud/cluster-api-provider-hcloud/releases/latest/infrastructure-components.yaml"
    type: "InfrastructureProvider"

• Deploy the cluster API components to the management cluster

clusterctl init --infrastructure hcloud:v0.1.0-rc.4

• Create your first cluster cluster-dev

# The location of the cluster (fsn1|hel1|nbg1)
export HCLOUD_LOCATION=fsn1
# Name of SSH keys that have access to the cluster, you need to upload them before
export HCLOUD_SSH_KEY_NAME=id_rsa
# Instance types used (cf. https://www.hetzner.com/cloud) 
# Caution! Do not use a cx11 for control-plane! Kubadm requires more than 1 vCPU
export HCLOUD_NODE_MACHINE_TYPE=cx21
export HCLOUD_CONTROL_PLANE_MACHINE_TYPE=cx21

# Create cluster yamls
clusterctl config cluster cluster-dev --kubernetes-version v1.18.3 --control-plane-machine-count=1 --worker-machine-count=3 > cluster-dev.yaml

# Apply the resources
kubectl apply -f cluster-dev.yaml

# Watch resources being created
watch -n 1 kubectl get hcloudclusters,cluster,hcloudmachines,machines,kubeadmcontrolplane

The cluster need some time until it is ready:

• Once the Control Plane has a ready replica, create a kubeconfig for the hcloud cluster and test connectivity:

KUBECONFIG_GUEST=$(pwd)/.kubeconfig-cluster-dev
kubectl get secrets cluster-dev-kubeconfig -o json | jq -r .data.value | base64 -d > $KUBECONFIG_GUEST
KUBECONFIG=$KUBECONFIG_GUEST kubectl get all,nodes -A

For Developers or demo purpose

Please use this for testing!

See ./docs/src/developers or https://docs.capihc.com/developer/developer.html

Prerequisites

• clusterctl

• docker

• kind

• kubectl

• kustomize

• kubebuilder

• packer

• BAZEL

• Go 1.13

• gomock

• watch (On MAC: brew install watch)

• JQ (On MAC: brew install jq)

• Running development version

This creates the management cluster with all the controllers

# Deploy kind cluster with cluster-api core componets
./demo/setup.sh

# Build project and deploy to local cluster
make deploy_kind

• Applying the target cluster with demo-cluster

# Please create an SSH Key for later access on the nodes.
ssh-keygen -t ed25519 -C "your_email@example.com" -f ~/.ssh/cluster

# Create a Project on Hetzner Cloud and upload the public key. 

# Create a token on Hetzner Cloud and apply it as secret
kubectl create secret generic hcloud-token --from-literal=token=$TOKEN

#For automatic installation of manifests we use ClusterResourceSets
kubectl apply -f demo/ClusterResourceSets

## You can choose which manifests should be applyed by setting the value of the labels under kind: Cluster

# Apply the manifest to your management cluster; cluster name is cluster-dev; use quickstart guide for getting access to the target cluster
kubectl apply -f ./demo/demo-cluster.yaml
or
kubectl apply -f ./demo/cluster-centos-8.yaml

## Get Logs:
kubectl logs -f deployment/capi-hcloud-controller-manager -c manager --v=4 -n capi-hcloud-system

# Deleting the target cluster
kubectl delete -f ./demo/demo-cluster.yaml

# Deleting the controller
make delete_capihc

# Deleting the management cluster
kind delete cluster --name capi-hcloud