Open twz123 opened 9 months ago
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
Before creating an issue, make sure you've checked the following:
Platform
Version
main
Sysinfo
`k0s sysinfo`
What happened?
When upgrading to Kubernetes v1.28.4, the CI kicked in before k0s's kube-proxy image was published.
Steps to reproduce
Change the kube-proxy image to something that doesn't exist and try the CI.
Expected behavior
The Autopilot update inttests detect that the cluster is not healthy and fail.
Actual behavior
The Autopilot tests completed successfully, while other tests failed.
Screenshots and logs
https://github.com/k0sproject/k0s/actions/runs/6888595027?pr=3716
Additional context
No response