1Feature: Linkerdctl restarts the workloads specified in the linkerdworkloadinjection CR
2
3Scenario: Linkerdworkloadinjection applied with empty namespaces and force set to false in spec
4 Given linkerdctl is healthy
5 And pods have the linkerd enabled annotation
6 And pods are running successfully
7 When a linkerdworkloadinjection CR is created with empty namespaces and force set to false
8 Then all pods with missing or outdated linkerd proxies that are not on the host network will be restarted
9 And the linkerd proxy is reinjected
10 And all containers within pods are running successfully
11
12Scenario: Linkerdworkloadinjection applied with empty namespaces and force set to true in spec
13 Given linkerdctl is healthy
14 And pods have the linkerd enabled annotation
15 And pods are running successfully
16 When a linkerdworkloadinjection CR is created with empty namespaces and force set to true
17 Then all pods that are not on the host network will be restarted
18 And the linkerd proxy is reinjected
19 And all containers within pods are running successfully
20
21Scenario: Linkerdworkloadinjection applied with specific namespaces and force set to false in spec
22 Given linkerdctl is healthy
23 And pods have the linkerd enabled annotation
24 And pods are running successfully
25 When a linkerdworkloadinjection CR is created with specific namespaces and force set to false
26 Then pods in the specified namespaces with missing or outdated linkerd proxies that are not on the host network will be restarted
27 And the linkerd proxy is reinjected
28 And all containers within pods are running successfully
29
30Scenario: Linkerdworkloadinjection applied with specific namespaces and force set to true in spec
31 Given linkerdctl is healthy
32 And pods have the linkerd enabled annotation
33 And pods are running successfully
34 When a linkerdworkloadinjection CR is created with specific namespaces and force set to true
35 Then pods in the specified namespaces that are not on the host network will be restarted
36 And the linkerd proxy is reinjected
37 And all containers within pods are running successfully
View as plain text