Chainguard Container for cyberark-secrets-provider-for-k8s-fips

The CyberArk Secrets Provider for Kubernetes provides Kubernetes-based applications with access to secrets that are stored and managed in Conjur.

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/cyberark-secrets-provider-for-k8s-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

Chainguard's cyberark-secrets-provider-for-k8s-fips image is comparable to the upstream image from CyberArk on Docker Hub.

FIPS Support

This Chainguard image ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

You can deploy an application container using Chainguard's cyberark-secrets-provider-for-k8s-fips image with Helm.

First, add the CyberArk Helm repository:

helm repo add cyberark https://cyberark.github.io/helm-charts
helm repo update

Then, deploy the secrets provider with the chart, substituting CyberArk's image with Chainguard's:

helm install secrets-provider cyberark/secrets-provider \
  -n <YOUR APPLICATION'S NAMESPACE> \
  --set secretsProvider.image=cgr.dev/ORGANIZATION/cyberark-secrets-provider-for-k8s-fips \
  --set secretsProvider.tag=latest \
  --set environment.k8sSecrets="{<YOUR K8S SECRET>}" \
  --set environment.conjur.conjurConnConfigMap=conjur-connect \
  --set environment.conjur.authnLogin="<YOUR APPLICATION'S HOST>"

Alternatively, you can deploy the secrets provider as an init container for your application. Please refer to the official documentation for more details.

Documentation and Resources

• Official documentation
• GitHub repository
• Helm chart

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.