Getting Started with kOps on Hetzner Cloud

WARNING: Hetzner Cloud support on kOps is currently in beta, which means it is in good shape and could be used for production. However, it is not as rigorously tested as the stable cloud providers and there are some features that might be missing.

Requirements

  • kOps version >= 1.24
  • kubectl version >= 1.23
  • Hetzner Cloud account
  • Hetzner Cloud token
  • SSH public and private keys
  • S3 compatible object storage (like MinIO)

Environment Variables

It is important to set the following environment variables:

  1. export HCLOUD_TOKEN=<token>
  2. export S3_ENDPOINT=<endpoint>
  3. export S3_ACCESS_KEY_ID=<acces-key>
  4. export S3_SECRET_ACCESS_KEY=<secret-key>
  5. export KOPS_STATE_STORE=s3://<bucket-name>

Some S3 compatible stores may also require to set the region:

  1. export S3_REGION=<region>

Creating a Single Master Cluster

In the following examples, example.k8s.local is a gossip-based DNS cluster name.

  1. # create a ubuntu 20.04 + calico cluster in fsn1
  2. kops create cluster --name=my-cluster.example.k8s.local \
  3.   --ssh-public-key=~/.ssh/id_rsa.pub --cloud=hetzner --zones=fsn1 \
  4.   --image=ubuntu-20.04 --networking=calico --network-cidr=10.10.0.0/16 
  5. kops update cluster my-cluster.example.k8s.local --yes
  7. # create a ubuntu 20.04 + calico cluster in fsn1 with CPU optimized servers
  8. kops create cluster --name=my-cluster.example.k8s.local \
  9.   --ssh-public-key=~/.ssh/id_rsa.pub --cloud=hetzner --zones=fsn1 \
  10.   --image=ubuntu-20.04 --networking=calico --network-cidr=10.10.0.0/16 \
  11.   --node-size cpx31
  12. kops update cluster --name=my-cluster.example.k8s.local --yes
  14. # update a cluster
  15. kops update cluster --name=my-cluster.example.k8s.local
  16. kops update cluster --name=my-cluster.example.k8s.local --yes
  17. kops rolling-update cluster --name=my-cluster.example.k8s.local
  18. kops rolling-update cluster --name=my-cluster.example.k8s.local --yes
  20. # validate a cluster
  21. kops validate cluster --name=my-cluster.example.k8s.local
  23. # delete a cluster
  24. kops delete cluster --name=my-cluster.example.k8s.local
  25. kops delete cluster --name=my-cluster.example.k8s.local --yes
  27. # export kubecfg
  28. # See https://kops.sigs.k8s.io/cli/kops_export_kubeconfig/#examples. 
  30. # update a cluster
  31. # See https://kops.sigs.k8s.io/operations/updates_and_upgrades/#manual-update.

Features Still in Development

kOps for Hetzner Cloud currently does not support the following features:

Next steps

Now that you have a working kOps cluster, read through the recommendations for production setups guide to learn more about how to configure kOps for production workloads.