For the complete documentation index, see llms.txt. This page is also available as Markdown.

FIPS-compliant installation

Configure Istio components to enforce FIPS cryptographic standards.

FIPS-compliant mode configures Istio components to enforce FIPS cryptographic standards. This is required for deployments in regulated environments.

This topic covers how you enable FIPS mode with either helm or clustermgr, and how you override the default compliance policy.


Enabling FIPS Mode

Enable FIPS mode at install time by setting the ingress type to Istio and turning on the fips input.

FIPS mode requires Istio ingress. Reuse the same Istio scenario files from Install with Istio, and add FIPS in your base override.yaml:

cluster:
  tfi:
    ingressType: istio
    fips: true

FIPS mode requires Istio ingress. Reuse the same Istio scenario parameters from Install with Istio, and add -i fips=true:

./clustermgr install-pi \
  --dns <DNS> \
  --email <EMAIL> \
  --password '<PASSWORD>' \
  --version <WORKFLOW_VERSION> \
  -i ingressType=istio \
  -i fips=true

When Istio is deployed by the Harness SMP Operator, this sets the COMPLIANCE_POLICY environment variable on both istiod (pilot) and istio-ingressgateway pods. The default compliance policy is fips-140-2.

Overriding the Compliance Policy

If your environment requires a standard other than the fips-140-2 default, set the compliance policy explicitly.

Set a different compliance policy in values.yaml:

cluster:
  tfi:
    fipsCompliancePolicy: fips-140-3

Pass the desired compliance policy:

-i fipsCompliancePolicy=fips-140-3
Input
Helm value
clustermgr input
Default
Description

fips

cluster.tfi.fips

-i fips=true

false

Enable FIPS-compliant mode

fipsCompliancePolicy

cluster.tfi.fipsCompliancePolicy

-i fipsCompliancePolicy=<policy>

fips-140-2

FIPS compliance policy for Istio components

For more information on FIPS compliance in Harness, see Harness FIPS Overview.

Last updated

Was this helpful?