-
Notifications
You must be signed in to change notification settings - Fork 700
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
Litmus Chaos Tests not running on K8s v1.27 #4125
Comments
I am also facing the same issue on Amazon EKS cluster (1.27), it works correctly on v 1.24. |
Same here ! With litmus 3.0.0-beta8 (and reproduced on 3.0.0-beta7 too) |
Able to reproduce on Minikube + containerd + litmus 3.0.0-beta8
case 2 : error group running kubernetes 1.27 Helper instantly killed We'll stick our clusters on kube 1.26.X (less than 1.27) on our side for now |
This is fixed in 3.00beta10 via litmuschaos/litmus-go#665 In 2.14.1 via litmuschaos/litmus-go#669 |
Based on the PRs, how does deleting labels fix the issue? The release notes state a kubelet flag but I don't see how that would impact starting the helper pods via the k8s API? EDIT: Or is it related to the standard labels that are added to pods since 1.27
|
@ksatchit can the 2.14.1 be pushed to dockerhub? |
What happened:
LitmusChaos tests not running properly on Kubernetes v1.27
What you expected to happen:
LitmusChaos tests should run properly on Kubernetes v1.27
Where can this issue be corrected? (optional)
The issue is probably in the source code of
litmuschaos/go-runner:2.14.0
How to reproduce it (as minimally and precisely as possible):
Note: Followed the instructions as per https://litmuschaos.github.io/litmus/experiments/categories/pods/pod-cpu-hog/.
Deploy litmus operator v2.14.0
Deploy below ChaosExperiment:
Create below RBAC:
Deploy below ChaosEngine:
Anything else we need to know?:
Log of
pod-cpu-hog-vczplk-d5fsw
pod created during experiemnt:Events from the Job that creates
pod-cpu-hog-vczplk-d5fsw
pod:It seems like the helper pod is getting deleted immediately after it is created.
The text was updated successfully, but these errors were encountered: