b16fae463e
Previously we pinned to 1.28/stable due to a bug that prevented 1.29/stable from working. Now we've hit a new issue with 1.28/stable on bookworm. The fix for that appears to simply be to upgrade to 1.31/stable so we do so here. More details can be found in this GitHub issue: https://github.com/canonical/microk8s/issues/4361 The new version appears to return from the snap installation before the k8s installation is fully ready to deal with add-on installation. This occasionally produces errors like: subprocess.CalledProcessError: Command '('/snap/microk8s/7178/microk8s-kubectl.wrapper', 'get', 'all,ingress', '--all-namespaces')' returned non-zero exit status 1. Work around that with `microk8s status --wait-ready` to ensure that k8s is up before adding addons. While we are at it we also update the collect-kubernetes-logs role to collect microk8s inspect output as that would've enabled us to debug the above issue without holding nodes. We also update test jobs to trigger when the collect-kubernetes-logs and collect-container-logs roles are updated to ensure we get coverage from those jobs when updating these roles. Change-Id: I60022ec6468c2cadd723a71bbc583f20096b27dc |
||
|---|---|---|
| .. | ||
| crio-default.yaml | ||
| crio-Ubuntu-18.04.yaml | ||
| crio-Ubuntu-20.04.yaml | ||
| crio-Ubuntu-22.04.yaml | ||
| main.yaml | ||
| microk8s.yaml | ||
| minikube.yaml | ||