leonsteinhaeuser/terraform-k8s-hcloud

This repository provides scripts that spin up a kubernetes cluster in the Hetzner cloud environment.

terraform-k8s-hcloud's Issues

etcd certificate creation failes during control plane cluster setup (hetzner_master_count > 1)

root@k8s-master-2:~# kubeadm join k8s.computingoverload.de:6443 --token <token>   --discovery-token-ca-cert-hash sha256:<hash>   --control-plane
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: missing optional cgroups: hugetlb
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[preflight] Running pre-flight checks before initializing the new control plane instance
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master-2 k8s.computingoverload.de kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.128.0.1 88.198.198.107]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Using the existing "etcd/healthcheck-client" certificate and key
error execution phase control-plane-prepare/certs: error creating PKI assets: failed to write or validate certificate "etcd-server": certificate etcd/server is invalid: x509: certificate is valid for k8s-master-1, localhost, not k8s-master-2
To see the stack trace of this error execute with --v=5 or higher

installation process with set k8s_external_kubernetes_address, requires manual intervention

Describe the bug
Manual intervention during cluster creation.

To Reproduce
Steps to reproduce the behavior:

1. Define the following config settings

k8s_external_kubernetes_address="k8s.example.local"

2. Use the following commands to build the infrastructure

terraform apply

3. What happened?

Currently, the user has to configure the dns-name manually at his dns-provider immediately after the master-node boot up.

Expected behavior
Run Kubernetes cluster without the need for further manual changes

Desktop (please complete the following information):

• OS: Debian
• Version: Buster (10)
• Terraform Version

Add nginx ingress controller as default

Initialize nginx ingress controller:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/baremetal/deploy.yaml

hcloud-provider hetzner datacenter=fsn1 not valid input

https://github.com/leonsteinhaeuser/terraform-hcloud/blob/fae68bced08e6de3b5c198864f47a357aafc4612/servers.tf#L13
https://github.com/leonsteinhaeuser/terraform-hcloud/blob/fae68bced08e6de3b5c198864f47a357aafc4612/servers.tf#L80

Error: datacenter 'nbg1' not found (invalid_input)

  on servers.tf line 7, in resource "hcloud_server" "k8s_nodes_master":
   7: resource "hcloud_server" "k8s_nodes_master" {

hcloud_loadbalancer selector is missing

To do:

• add service selector (ports: 80, 443, 6443, ...)
• add node selector (k8s-master-*)