Try It Out
In this example we will deploy Argo Rollouts on a Kubernetes cluster using the Minimus Argo Rollouts Helm chart. Argo Rollouts provides advanced deployment strategies including canary and blue-green deployments for your Kubernetes workloads.
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Create Namespace
Create a namespace:
kubectl create ns argo-rollouts
Step 3: Deploy the Helm Chart
Deploy the Minimus Helm chart:
helm install my-argo-rollouts oci://helm.mini.dev/argo-rollouts \
--version 2.43.0 \
-n argo-rollouts \
--wait
If you want to override the chart's defaults, go to the Values tab and save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:
helm install my-argo-rollouts oci://helm.mini.dev/argo-rollouts \
--version 2.43.0 \
-f values.yaml \
-n argo-rollouts \
--wait
By default, the controller manages Rollouts via CRDs and has no web UI. Below is a values.yaml example that enables the dashboard on port 3100 so you can inspect canary steps and promote or abort rollouts without the kubectl argo rollouts CLI:
argo-rollouts:
imagePullSecrets:
- name: minimus-registry
controller:
image:
registry: reg.mini.dev
repository: argo-rollouts-fips
tag: "v1.9.0"
dashboard:
enabled: true
service:
type: ClusterIP
port: 3100
ingress:
enabled: false
ClusterIP exposes the dashboard only inside the cluster (for example via kubectl port-forward). Set ingress.enabled: true when you want a hostname for team access.
Step 4: Verify Argo Rollouts is Running
Confirm the chart deployed successfully and Argo Rollouts started:
kubectl get pods -n argo-rollouts
You should see output similar to:
NAME READY STATUS RESTARTS AGE
my-argo-rollouts-argo-rollouts-xxxxxxxxx-xxxxx 1/1 Running 0 2m
my-argo-rollouts-argo-rollouts-xxxxxxxxx-xxxxx 1/1 Running 0 2m
Step 5: Test Argo Rollouts Controller
Verify that the Argo Rollouts CRDs are installed and the controller is operational:
kubectl get crd rollouts.argoproj.io
You should see the Rollout CRD listed.
Next, create a sample Rollout to verify the controller processes it:
kubectl apply -n argo-rollouts -f - <<EOF
apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
name: test-rollout
spec:
replicas: 1
selector:
matchLabels:
app: test-rollout
template:
metadata:
labels:
app: test-rollout
spec:
containers:
- name: nginx
image: nginx:stable
ports:
- containerPort: 80
strategy:
canary:
steps:
- setWeight: 100
EOF
Check the Rollout status:
kubectl get rollout test-rollout -n argo-rollouts
Clean up the test Rollout:
kubectl delete rollout test-rollout -n argo-rollouts
Step 6: Clean Up
Uninstall the chart and delete the namespace to remove all resources:
helm uninstall my-argo-rollouts -n argo-rollouts
kubectl delete namespace argo-rollouts
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.
kubectl-argo-rollouts v1.10.0