Chainguard Container for newrelic-kubernetes-fips

FIPS-compliant minimal newrelic-kubernetes container image.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/newrelic-kubernetes-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard newrelic-kubernetes-fips image is a FIPS 140-2/140-3 compliant version designed to be a drop-in replacement for the upstream newrelic/nri-kubernetes image in FIPS-required environments. This image integrates seamlessly with the New Relic Infrastructure agent to provide comprehensive Kubernetes monitoring capabilities.

For non-FIPS environments, see newrelic-kubernetes.

FIPS support

The newrelic-kubernetes-fips Chainguard Image ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Getting Started

The newrelic-kubernetes-fips images are drop-in replacements for the upstream newrelic project. The images are tested against the upstream recommended nri-bundle Helm chart.

Helm Installation

Add the New Relic Helm repository and install the nri-bundle with FIPS images:

helm repo add newrelic https://helm-charts.newrelic.com
helm repo update

Create a values file for the FIPS-compliant installation:

cat > fips-values.yaml <<EOF
global:
  cluster: $CLUSTER_NAME
  licenseKey: $LICENSE_KEY

newrelic-infrastructure:
  images:
    agent:
      registry: cgr.dev
      repository: ORGANIZATION/newrelic-infrastructure-bundle-fips
      tag: latest
    integration:
      registry: cgr.dev
      repository: ORGANIZATION/newrelic-kubernetes-fips
      tag: latest
EOF

Install the Helm chart with the FIPS values:

helm install nri-bundle newrelic/nri-bundle \
  --namespace newrelic \
  --create-namespace \
  -f fips-values.yaml

Be sure to replace ORGANIZATION with your organization's name in the Chainguard Registry, $CLUSTER_NAME with your cluster identifier, and $LICENSE_KEY with your New Relic license key.

For advanced configuration options including resource limits, custom attributes, and integration settings, refer to the official New Relic Kubernetes integration documentation.

Documentation and Resources

• New Relic Kubernetes Integration Documentation
• nri-bundle Helm Chart
• GitHub Repository

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.