4 Commits
0.1.3 ... 0.1.5

Author SHA1 Message Date
183112d67a feat: release 0.1.5
All checks were successful
release-image-gitea / build (push) Successful in 1m26s
test-build / guarddog (push) Successful in 1m30s
renovate / renovate (push) Successful in 2m13s
release-image-harbor / build (push) Successful in 3m22s
test-build / build (push) Successful in 3m29s
release-image-gitea / release (push) Successful in 4m12s
release-image-harbor / release (push) Successful in 10m55s
2026-02-18 21:25:51 -06:00
6df4aecf68 fix: titles of docs 2026-02-18 21:25:24 -06:00
67a6039bb3 feat: release 0.1.4
All checks were successful
renovate / renovate (push) Successful in 3m13s
test-build / guarddog (push) Successful in 2m29s
test-build / build (push) Successful in 5m4s
release-image-gitea / build (push) Successful in 1m0s
release-image-harbor / build (push) Successful in 2m16s
release-image-harbor / release (push) Successful in 4m30s
release-image-gitea / release (push) Successful in 8m24s
2026-02-18 18:08:45 -06:00
b392500fe5 feat: add talos upgrade docs 2026-02-18 18:08:10 -06:00
4 changed files with 71 additions and 3 deletions

View File

@@ -28,7 +28,7 @@ ENV HOST=0.0.0.0
ENV SITE_URL=https://docs.alexlebens.dev ENV SITE_URL=https://docs.alexlebens.dev
ENV PORT=4321 ENV PORT=4321
LABEL version="0.1.3" LABEL version="0.1.5"
LABEL description="Astro based documentation website" LABEL description="Astro based documentation website"
EXPOSE $PORT EXPOSE $PORT

View File

@@ -1,7 +1,7 @@
{ {
"name": "site-documentation", "name": "site-documentation",
"type": "module", "type": "module",
"version": "0.1.3", "version": "0.1.5",
"scripts": { "scripts": {
"dev": "astro dev", "dev": "astro dev",
"build": "astro build", "build": "astro build",

View File

@@ -1,5 +1,5 @@
--- ---
title: Talos Upgrade title: Talos Upgrade 1.12.0
description: Steps followed for the v1.12.0 upgrade process description: Steps followed for the v1.12.0 upgrade process
--- ---

View File

@@ -0,0 +1,68 @@
---
title: Talos Upgrade Generic
description: Steps followed for the standard upgrade process
---
This is the standard upgrade process for Talos. Relatively simple, just verify, run commands, and verify.
## Health Check
### Etcd
Check status of etcd, ensure there is a leader and there are no errors.
```bash
talosctl -n 10.232.1.11,10.232.1.12,10.232.1.13 etcd status
```
### Ceph
Check if ceph is healthy:
Either browse to the [webpage](https://ceph.alexlebens.net/#/dashboard), or run the following commands on the tools container
```bash
kubectl -n rook-ceph exec -it $(kubectl -n rook-ceph get pod -l "app=rook-ceph-tools" -o jsonpath='{.items\[\*].metadata.name}') -- bash
```
Inside the rook-ceph-tools container check the status:
```bash
ceph status
```
### Cloudnative-PG
Check the status of the Cloudnative-PG clusters to ensure they are all healthy. There is potential data loss if a worker node has a failure or the local volume isn't reattached.
[Dashboard](https://grafana.alexlebens.net/d/cloudnative-pg/cloudnativepg)
### Garage
Check the status of the Garage cluster to ensure there is no data loss of the local S3 store. This will result in data loss of short term WALs if this cluster fails
[Dashboard](https://garage-webui.alexlebens.net/)
## Upgrade
Reference the [config repo](https://gitea.alexlebens.dev/alexlebens/talos-config/src/branch/main) for the exact commands, links to the factory page, and update the image versions. Each type has its own image string.
As an example to upgrade a NUC node:
```bash
talosctl upgrade --nodes 10.232.1.23 --image factory.talos.dev/metal-installer/495176274ce8f9e87ed052dbc285c67b2a0ed7c5a6212f5c4d086e1a9a1cf614:v1.12.0
```
# Apply new configuration
Use the generate command in the README of the talos-config repo to make the configuration to be supplied.
As an example to apply that generated config to a NUC node:
```bash
talosctl apply-config -f generated/worker-nuc.yaml -n 10.232.1.23
```
## Verification
Verify all is health on the dashboard:
```bash
talosctl -n 10.232.1.23 dashboard
```