Investgate why test cases gr-self-healing and gr-self-healing have different DaemonSets for the different operators
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:
Details
Details
Assignee
Julio Pasinatto
Julio PasinattoReporter
Pavel Tankov
Pavel Tankov(Deactivated)Needs QA
Yes
Story Points
3
Components
Sprint
Fix versions
Affects versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created February 4, 2025 at 1:01 PM
Updated February 17, 2025 at 2:02 PM
Test cases
gr-self-healingandgr-self-healingare unstable. Problem is the assert statement in the kuttl framework, because currently we’re expecting this:apiVersion: apps/v1 kind: DaemonSet metadata: name: chaos-daemon status: currentNumberScheduled: 3 desiredNumberScheduled: 3 numberAvailable: 3 numberMisscheduled: 0 numberReady: 3 observedGeneration: 1 updatedNumberScheduled: 3but depending on the k8s platform the numbers of
currentNumberScheduled,desiredNumberScheduled,numberAvailable,numberReady,updatedNumberScheduledare 3 for EKS and 4 for GKE and Minikube. In the past, we had the whole section removed, then it was re-introduced again. We need to decide whether we will remove it or we will have platform specific asserts.