argo-rollouts-fips

The Argo Rollouts FIPS Helm chart automates deployment and configuration of Argo Rollouts in Kubernetes clusters using the Minimus Argo Rollouts FIPS-validated images. Argo Rollouts is a Kubernetes controller and set of CRDs which provide advanced deployment capabilities such as blue-green, canary, canary analysis, experimentation, and progressive delivery features to Kubernetes.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges are required for CRD installation and cluster-scoped RBAC

Note: Argo Rollouts installs Custom Resource Definitions (CRDs) such as Rollout, AnalysisTemplate, and Experiment. Cluster Admin privileges are required.

FIPS Validated Images

This chart deploys FIPS 140-3 validated images provided and maintained by Minimus. View the images for FIPS validation details.

Try It Out

In this example we will deploy Argo Rollouts on a Kubernetes cluster using the Minimus Argo Rollouts FIPS Helm chart. Argo Rollouts will provide 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-fips

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-argo-rollouts-fips oci://helm.mini.dev/argo-rollouts-fips \
  --version 2.41.0 \
  -n argo-rollouts-fips \
  --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-fips oci://helm.mini.dev/argo-rollouts-fips \
  --version 2.41.0 \
  -f values.yaml \
  -n argo-rollouts-fips \
  --wait

Step 4: Verify Argo Rollouts is Running

Confirm the chart deployed successfully and Argo Rollouts started:

kubectl get pods -n argo-rollouts-fips

You should see output similar to:

NAME                                                       READY   STATUS    RESTARTS   AGE
my-argo-rollouts-fips-argo-rollouts-xxxxxxxxx-xxxxx   1/1     Running   0          2m
my-argo-rollouts-fips-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-fips -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-fips

Clean up the test Rollout:

kubectl delete rollout test-rollout -n argo-rollouts-fips

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-argo-rollouts-fips -n argo-rollouts-fips
kubectl delete namespace argo-rollouts-fips

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.

This page is available on desktop