istio
Upgrade to Istio 1.13.3
No issues whatsoever by manually upgrading by means of istioctl. Istio 1.13.3
k3s
k3s
Upgrade to K3s v1.22.8+k3s1
Manual minor upgrade without any issues om both arm and intel architecture. v1.22.8+k3s1
istio
Upgrade to Istio 1.13.2
No issues whatsoever by manually upgrading by means of istioctl. Istio 1.13.2 curl -L https://istio.io/downloadIstio | ISTIO_VERSION=1.13.2 TARGET_ARCH=x86_64 sh - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 101 100 101
metallb
Upgrade to MetalLB v0.12.1
No problems whatsoever by manually applying hte MetalLB manifest yaml files on both architectures - arm64 and amd64. v0.12.1
k3s
Upgrade to K3s v1.22.7+k3s1
Manual minor upgrade without any issues om both arm and intel architecture. v1.22.7+k3s1
k3s
Upgrade to K3s v1.21.10+k3s1
Manual micro upgrade without any issues om both arm and intel architecture. v1.21.10+k3s1
GitLab
Upgrade of GitLab Runner 14.3.2
No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. v14.3.2
GitLab
Upgrade of GitLab Runner 14.3.1
No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. v14.3.0 v14.3.1
ghost
Upgrade to Ghost 4.12.1
On both domains I upgraded Ghost successfully by means of Flux V2 K3s cluster reconciliation. v4.12.0 v4.12.1
GitLab
Upgrade of GitLab Runner 14.2.0
No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. v14.2.0
portainer
Upgrade to Portainer Agent 2.6.2
Successful micro upgrade by means of Watchtower infrastructure with manual recreation of container. Release 1.6.1 portainer/agent:2.6.2-alpine
GitLab
Upgrade to GitLab Runner 14.1.0
No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. v14.1.0