2021-07-30 10:12:37 +02:00
|
|
|
terraform {
|
|
|
|
|
required_providers {
|
2022-01-13 13:32:17 +01:00
|
|
|
github = {
|
|
|
|
|
source = "integrations/github"
|
|
|
|
|
version = ">= 4.0.0, < 5.0.0"
|
|
|
|
|
}
|
2021-07-30 10:12:37 +02:00
|
|
|
hcloud = {
|
|
|
|
|
source = "hetznercloud/hcloud"
|
2022-01-13 09:53:00 +01:00
|
|
|
version = ">= 1.0.0, < 2.0.0"
|
2021-07-30 10:12:37 +02:00
|
|
|
}
|
2022-01-13 12:36:10 +01:00
|
|
|
local = {
|
|
|
|
|
source = "hashicorp/local"
|
|
|
|
|
version = ">= 2.0.0, < 3.0.0"
|
|
|
|
|
}
|
Expose kubeconfig in outputs...
* To do so, we need to ensure that the generated kubeconfig is part of
terraforms dependency graph. This has the additional benefit of not
depending on local files anymore which should enable multi-user
setups.
* This also means that we can't deploy CCM, CSI & Traefik from our local
host, because we don't have kubeconfig.yaml locally while provisioning
the control plane, only afterwards.
* So we just run kubectl apply on the control plane itself, after k3s is
ready.
* To do so, we need to deploy all manifests. I've merged the patches
into a single kustomization.yaml file, because that makes the
deployment of those files to the control-plane server easier.
* we could also put the traefik config into the same kustomization file,
which would save us one of the file provisioner blocks. I didn't want
this PR to get any bigger, and will consider merging this config later
on. kustomization.yaml is small enough that we could yamlencode() for
it and store the patches in separate files again, not as
inline-strings which is kind of ugly.
2022-02-11 12:45:03 +01:00
|
|
|
remote = {
|
|
|
|
|
source = "tenstad/remote"
|
2022-10-26 17:16:22 +02:00
|
|
|
version = "~> 0.1.23"
|
Expose kubeconfig in outputs...
* To do so, we need to ensure that the generated kubeconfig is part of
terraforms dependency graph. This has the additional benefit of not
depending on local files anymore which should enable multi-user
setups.
* This also means that we can't deploy CCM, CSI & Traefik from our local
host, because we don't have kubeconfig.yaml locally while provisioning
the control plane, only afterwards.
* So we just run kubectl apply on the control plane itself, after k3s is
ready.
* To do so, we need to deploy all manifests. I've merged the patches
into a single kustomization.yaml file, because that makes the
deployment of those files to the control-plane server easier.
* we could also put the traefik config into the same kustomization file,
which would save us one of the file provisioner blocks. I didn't want
this PR to get any bigger, and will consider merging this config later
on. kustomization.yaml is small enough that we could yamlencode() for
it and store the patches in separate files again, not as
inline-strings which is kind of ugly.
2022-02-11 12:45:03 +01:00
|
|
|
}
|
2021-07-30 10:12:37 +02:00
|
|
|
}
|
|
|
|
|
}
|
