Max

We found that configuring the serviceaccount to use imagepullsecrets also works as an alternative: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account but going to keep this open as the issue itself is still valid as an...

CI can be switched over now whenever as I've closed the mentioned issue

This has been fixed and validated in v1.25.2-rc1+k3s1 via the new k8s version. Thank you for all the details on this issue! You will see the fixes when the release...

https://github.com/rancher/rancher/issues/38701

This needs the following NetworkPolicies as well and then it seems to work: ``` apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-all-svclbtraefik-ingress namespace: kube-system spec: ingress: - {} podSelector: matchLabels: svccontroller.k3s.cattle.io/svcname:...

A few edits: 1. Renamed issue title from `Node fails to properly delete after an upgrade`. An upgrade made this easier to reproduce since it can often change the leader...

This is no longer happening. The logs on the deleted node now repeat with the following panic: ```log Feb 27 21:57:36 ip-172-31-1-62 k3s[12066]: {"level":"info","ts":"2023-02-27T21:57:36.431Z","caller":"rafthttp/peer.go:335","msg":"stopped remote peer","remote-peer-id":"7717fe38937f907a"} Feb 27 21:57:36 ip-172-31-1-62...

### Validated on release-1.25 branch with commit `457e5e7379821db3feed65548fb7678345a73828` and master branch with commit `b5d39df9294627cbfa3081acb92e2be54f02b0d6`   ## Environment Details   *Infrastructure* - [x] Cloud (AWS) - [ ] Hosted   *Node(s) CPU architecture, OS,...

### Validated using v1.30.0-rc2+k3s1 and v1.30.0-rc2+rke2r1 This log warning is no longer present. See only deprecation warning remaining: ``` $ journalctl -eu k3s | grep -i deprecated May 08 19:14:42...

Sure, bumped and put to Needs Additional status as it "needs additional work/information for when there are vulns"