argo-rollouts-gateway-api-router-fips

Fips

Infra

Stig

Updated 23 hours ago

Argo Rollouts Gateway API Router FIPS Overview

Secure your stack with a hardened, FIPS-validated Argo Rollouts Gateway API Router image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Argo Rollouts Gateway API Router is a traffic routing plugin that integrates Argo Rollouts with the standard Kubernetes Gateway API. It is used to dynamically split and shift live web traffic across HTTPRoute resources during progressive delivery strategies like canary or blue-green deployments.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

Prerequisites

A running Kubernetes cluster (v1.21 or higher is recommended)
Helm v3.8 or higher for OCI support (Installation instructions)
kubectl installed and configured
Kubernetes Gateway API CRDs installed (Installation instructions)

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Add Repository to Your Local Client

Add the official Helm chart repository to your local Helm client:

helm repo add argo https://argoproj.github.io/argo-helm
helm repo update

Step 3: Override Chart Defaults

Save the following to a values.yaml file in your working directory. This configures Argo Rollouts to load the plugin binary from the Minimus image via an init container:

controller:
  image:
    registry: reg.mini.dev
    repository: argo-rollouts-fips
    tag: latest
  initContainers:
    - name: plugin-init
      image: reg.mini.dev/argo-rollouts-gateway-api-router-fips:latest
      command:
        - sh
        - -c
        - cp /usr/bin/rollouts-plugin-trafficrouter-gatewayapi /tmp/rollout-plugins/trafficrouter-gatewayapi
      volumeMounts:
        - name: rollout-plugins
          mountPath: /tmp/rollout-plugins
  volumes:
    - name: rollout-plugins
      emptyDir: {}
  volumeMounts:
    - name: rollout-plugins
      mountPath: /home/argo-rollouts/plugins
imagePullSecrets:
  - name: minimus-registry

Render the chart locally with the overrides to confirm Minimus images will be deployed:

helm template argo-rollouts argo/argo-rollouts -f values.yaml  | grep "reg.mini.dev"

Step 4: Deploy Argo-Rollouts with the Plugin

Run the following command from your working directory (where the values.yaml is located):

helm upgrade --install argo-rollouts argo/argo-rollouts \
  --namespace argo-rollouts \
  -f values.yaml

Wait a minute and check that the Pods are up and running:

kubectl -n argo-rollouts get po

Verify that the plugin binary was loaded by checking the init container completed successfully:

kubectl -n argo-rollouts describe pod -l app.kubernetes.io/name=argo-rollouts | grep -A5 "Init Containers"

Clean Up

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

Technical Considerations

The Argo Rollouts Gateway API Router FIPS image provided by Minimus is a slim, security-hardened, FIPS-validated alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Argo Rollouts Gateway API Router FIPS built by Minimus:

Uses a FIPS 140-3 validated cryptographic module, suitable for FedRAMP and other federal compliance frameworks.
Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

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.