Adding drain_reboot_cron: true for missing nodes

This commit is contained in:
Mikael Andersson 2025-02-17 14:18:09 +01:00
parent e86ee48916
commit 6dd96bafed
Signed by: mikand
GPG key ID: 184EEE05D37D72DF
2 changed files with 3 additions and 1 deletions

View file

@ -108,4 +108,4 @@ This will disrupt the whole cluster for a few seconds.
Install Velero backup from https://github.com/vmware-tanzu/velero/releases
velero install --provider aws --plugins velero/velero-plugin-for-aws:v1.2.1 --bucket velero --secret-file ./credentials-velero --use-volume-snapshots=false --backup-location-config region=sto3,s3ForcePathStyle="true",s3Url=https://s3.sto3.safedc.net
velero backup create rut-backup --selector 'backup notin (ignore)'
velero backup create rut-backup --selector 'backup notin (ignore)'

View file

@ -39,6 +39,7 @@
rut::infra_ca_rp:
sunet::microk8s::node:
channel: 1.31/stable
drain_reboot_cron: true
sunet::otel::alloy:
otel_receiver: monitor-prod.rut.sunet.se
sunet::fleetlock_client:
@ -85,6 +86,7 @@ internal-sto4-prod-satosa-1.rut.sunet.se:
rut::infra_ca_rp:
sunet::microk8s::node:
channel: 1.31/stable
drain_reboot_cron: true
sunet::otel::alloy:
otel_receiver: monitor-prod.rut.sunet.se
sunet::fleetlock_client: