Argo Rollouts

KICK can restart Argo Rollouts workloads when the Rollouts integration is enabled.

Enable the integration

Set one of the supported toggles:

• Helm value: integrations.argoRollouts.enabled: true
• Manager flag: --enable-argo-rollouts=true

Proof: Configuration reference.

Minimal policy

apiVersion: kick.corewire.io/v1alpha1
kind: KickPolicy
metadata:
  name: default
  namespace: kick-e2e-060
spec:
  discovery:
    workloadSelector: {}

Proof scenario: KICK-E2E-060.

Raw test manifest (implementation detail): resources.yaml.

Restart behavior that matters

KICK restarts Rollouts through spec.restartAt, not by patching pod-template annotations. That avoids re-running canary/blue-green steps from step zero.

Proof scenario:

• KICK-E2E-060

WorkloadRef behavior

For a Rollout with workloadRef, KICK targets the referenced Deployment when that Deployment owns the dependency.

Proof scenario:

• KICK-E2E-063

More proven examples

• Canary restart keeps step index: KICK-E2E-060
• Blue/green active service remains stable: KICK-E2E-061
• Rollout completion gates KickRequest: KICK-E2E-062

Feature mapping

• Argo Rollout workload restarts: KICK-FEAT-024