-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revamp TalosOS Provisioning & Bootstrapping. (#20)
* Change from individual paches to Jinjia Template. * Migrate to dagger functions. * Daggerize most of k8s initalization. * Update docs for daggerized Talos. * Revamped Talos Bootstraping & Provisioning.
- Loading branch information
Showing
24 changed files
with
405 additions
and
207 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# Starting from Scratch | ||
|
||
First, make sure to create the Talos VMs as described [here](/pve/talos_vms.html), | ||
then, `cd` into the `talos` directory. | ||
|
||
From here, you can use Dagger to automatically provision the nodes. Each step | ||
is also detailed in the sub-chapters - if you would prefer a manual approach. | ||
|
||
```bash | ||
$ dagger functions | ||
Name Description | ||
argocd Step 4: Start ArgoCD. | ||
base-img Builds a Alpine image with talosctl installed and ready to go. | ||
bootstrap Step 2: Bootstrap etcd. | ||
cilium Step 3: Apply Cilium. | ||
provision Step 1: Provision the nodes. | ||
``` | ||
|
||
# Step 1: Provision the Nodes | ||
|
||
After the brand new Talos VMs load up - and the `STAGE` is `Maintance` - run: | ||
|
||
```bash | ||
dagger call \ | ||
--raw-template-file=./templates/talos.yaml.j2 \ | ||
--talos-dir=_out \ | ||
provision | ||
``` | ||
|
||
# Step 2: Bootstrap Etcd | ||
|
||
After all the nodes have rebooted (~1min), bootstrap Etcd. The `STAGE` on | ||
`teemo` will change from `Installing` to `Booting` when its ready to be | ||
bootstraped. | ||
|
||
```bash | ||
dagger call \ | ||
--raw-template-file=./templates/talos.yaml.j2 \ | ||
--talos-dir=_out \ | ||
bootstrap | ||
``` | ||
|
||
# Step 3: Apply Cilium | ||
|
||
Once Etcd has started, apply cilium: | ||
|
||
```bash | ||
dagger call \ | ||
--raw-template-file=./templates/talos.yaml.j2 \ | ||
--talos-dir=_out \ | ||
cilium | ||
``` | ||
|
||
# Step 4: Start ArgoCD | ||
|
||
Once the Cilium step has compleated (it'll show a nice status dashboard), start ArgoCD. | ||
|
||
```bash | ||
dagger call \ | ||
--raw-template-file=./templates/talos.yaml.j2 \ | ||
--talos-dir=_out \ | ||
argocd | ||
``` | ||
Importantly, this step ends by printing out the default ArgoCD password. **You | ||
still need to manually change the password and sync the apps-of-apps; see | ||
[here](/k8s/argocd.html).** |
File renamed without changes.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
{ | ||
"name": "talos", | ||
"sdk": "python", | ||
"source": "dagger", | ||
"engineVersion": "v0.10.1" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
/sdk/** linguist-generated |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
/sdk |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[project] | ||
name = "main" | ||
version = "0.0.0" | ||
dependencies = [ | ||
"Jinja2", | ||
] |
Oops, something went wrong.