-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when draining pods with kubernetes upgrade #2866
Comments
Our instructions on how to install the system upgrade controller needed updating (see here). This seems to be related to missing rbac permissions and it may be solved by installing the latest following the new instructions. Let me finish documenting the installation and we can check if this one is fixed. |
Ok, thanks for the update. Il will give it a try when the documentation is up to date. |
I tried with the new instruction (see the linked PR) and build from kairos master and it works as expected:
(that's the |
I confirm that works. |
I think somehow the
The question is, why? |
We are supposed to put the tag in the Then what is the |
Version is used to update the Plan resource from what I see in the code. In any case, I don't see any concatenation happening: https://github.com/rancher/system-upgrade-controller/blob/f7f79ff18733b3c67ef0860db635abcf2391430f/pkg/upgrade/container/container.go#L93
I wonder if that changed recently (since we now install a latest system-upgrade-controller version). There used to be some concatenation happening: rancher/system-upgrade-controller@a24fafac#diff-a5a8b751c9bff70762c3ffd1f66c5107a837dafce0e220a84b317110e88bb45dL69 but that's from 2020... Maybe the example was based on that old version? |
I actually already had the "latest" tag on the image field...
|
Then that image doesn't have |
Ok, thanks for the advice. |
Thank you for you contribution @nicolaspernoud! It's impossible to keep a project polished (docs included), if users don't report the issues they find, so keep it coming! |
For future reference and for the sake of completeness, concatenation does happen here:
and I also checked with a plan like this:
and the image that it tried to pull was
which proves it concatenates. TL;DR; no documentation change is needed. |
Kairos version:
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
KAIROS_VERSION="v3.1.2-v1.30.4-k3s1"
KAIROS_IMAGE_LABEL="24.04-standard-amd64-generic-v3.1.2-k3sv1.30.4-k3s1"
KAIROS_FLAVOR_RELEASE="24.04"
KAIROS_HOME_URL="https://github.com/kairos-io/kairos"
KAIROS_ID="kairos"
KAIROS_ARTIFACT="kairos-ubuntu-24.04-standard-amd64-generic-v3.1.2-k3sv1.30.4+k3s1"
KAIROS_REGISTRY_AND_ORG="quay.io/kairos"
KAIROS_BUG_REPORT_URL="https://github.com/kairos-io/kairos/issues"
KAIROS_SOFTWARE_VERSION_PREFIX="k3s"
KAIROS_NAME="kairos-standard-ubuntu-24.04"
KAIROS_PRETTY_NAME="kairos-standard-ubuntu-24.04 v3.1.2-v1.30.4-k3s1"
KAIROS_IMAGE_REPO="quay.io/kairos/ubuntu:24.04-standard-amd64-generic-v3.1.2-k3sv1.30.4-k3s1"
KAIROS_VARIANT="standard"
KAIROS_MODEL="generic"
KAIROS_TARGETARCH="amd64"
KAIROS_RELEASE="v3.1.2"
KAIROS_GITHUB_REPO="kairos-io/kairos"
KAIROS_ID_LIKE="kairos-standard-ubuntu-24.04"
KAIROS_VERSION_ID="v3.1.2-v1.30.4-k3s1"
KAIROS_FLAVOR="ubuntu"
KAIROS_FAMILY="ubuntu"
CPU architecture, OS, and Version:
Linux *** 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Describe the bug
When running a kubernetes update following https://kairos.io/docs/upgrade/kubernetes/, the existing pods aren't deleted.
So the update does not start.
To Reproduce
Upgrade like explained in the documentation
Expected behavior
The upgrade should run.
Logs
kubectl -n system-upgrade logs apply-custom-os-upgrade-on-**** -c drain
gives :The text was updated successfully, but these errors were encountered: