Feature: Linkerdctl restarts the workloads specified in the linkerdworkloadinjection CR

Scenario: Linkerdworkloadinjection applied with empty namespaces and force set to false in spec
    Given linkerdctl is healthy
    And pods have the linkerd enabled annotation
    And pods are running successfully
    When a linkerdworkloadinjection CR is created with empty namespaces and force set to false
    Then all pods with missing or outdated linkerd proxies that are not on the host network will be restarted
    And the linkerd proxy is reinjected
    And all containers within pods are running successfully

Scenario: Linkerdworkloadinjection applied with empty namespaces and force set to true in spec
    Given linkerdctl is healthy
    And pods have the linkerd enabled annotation
    And pods are running successfully
    When a linkerdworkloadinjection CR is created with empty namespaces and force set to true
    Then all pods that are not on the host network will be restarted
    And the linkerd proxy is reinjected
    And all containers within pods are running successfully

Scenario: Linkerdworkloadinjection applied with specific namespaces and force set to false in spec
    Given linkerdctl is healthy
    And pods have the linkerd enabled annotation
    And pods are running successfully
    When a linkerdworkloadinjection CR is created with specific namespaces and force set to false
    Then pods in the specified namespaces with missing or outdated linkerd proxies that are not on the host network will be restarted
    And the linkerd proxy is reinjected
    And all containers within pods are running successfully

Scenario: Linkerdworkloadinjection applied with specific namespaces and force set to true in spec
    Given linkerdctl is healthy
    And pods have the linkerd enabled annotation
    And pods are running successfully
    When a linkerdworkloadinjection CR is created with specific namespaces and force set to true
    Then pods in the specified namespaces that are not on the host network will be restarted
    And the linkerd proxy is reinjected
    And all containers within pods are running successfully