sap-btp-service-operator-fips

packaged by Chainguard

Chainguard Container for sap-btp-service-operator-fips

A minimal, wolfi-based FIPS-compliant image of the SAP BTP Service Operator, a Kubernetes operator that enables consumption of SAP BTP services via native ServiceInstance and ServiceBinding custom resources.

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/sap-btp-service-operator-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

This is the FIPS-enabled variant of the Chainguard sap-btp-service-operator image. It is comparable to the upstream ghcr.io/sap/sap-btp-service-operator/controller image, with the following differences:

• The operator binary is built against a FIPS-validated cryptographic module (BoringCrypto/OpenSSL) and the image ships the FIPS-hardened OpenSSL configuration, so cryptography runs in FIPS mode (GODEBUG=fips140=on).
• Like all Chainguard Containers, it features a stripped-down, minimal design with few-to-zero CVEs and contains only the operator binary and its runtime dependencies — no shell or package manager.
• The image runs as a non-root user by default.

FIPS images are part of Chainguard's FIPS program and are available to customers with a FIPS-enabled account. Contact Chainguard for access.

Getting Started

The operator is intended to be installed with the upstream Helm chart, pointed at this image. It requires cert-manager for its admission-webhook TLS certificate, plus SAP Service Manager credentials and a cluster id.

Create a values.yaml supplying your SAP Service Manager credentials and pointing the chart at the Chainguard images. The chart pulls three images — the operator itself, a kube-rbac-proxy sidecar, and a kubectl helper used by its pre-delete hook — so override all three to run an all-Chainguard deployment. Keep manager.fips at its default (fips140=on): it sets GODEBUG=fips140=on on the operator, which is what puts this image's cryptography into FIPS-enforcing mode.

cluster:
  id: <cluster-id>
manager:
  fips: "fips140=on"
  image:
    repository: cgr.dev/ORGANIZATION/sap-btp-service-operator-fips
    tag: latest
    sha: ""
  rbacProxy:
    image:
      repository: cgr.dev/ORGANIZATION/kube-rbac-proxy-fips
      tag: latest
      sha: ""
  secret:
    clientid: <sm-client-id>
    clientsecret: <sm-client-secret>
    sm_url: <service-manager-url>
    tokenurl: <auth-url>
externalImages:
  kubectl:
    image:
      repository: cgr.dev/ORGANIZATION/kubectl-fips
      tag: latest
      sha: ""

helm upgrade --install sap-btp-operator \
  https://github.com/SAP/sap-btp-service-operator/releases/download/<version>/sap-btp-operator-<version>.tgz \
  --namespace sap-btp-operator --create-namespace \
  --values values.yaml

Once the operator is running, consume SAP BTP services with the ServiceInstance and ServiceBinding custom resources, exactly as with the non-FIPS image (the operator provisions the instance through SAP Service Manager and writes the binding credentials into a Kubernetes Secret).

FIPS Compliance

These FIPS-compliant images include OpenSSL FIPS provider and are built with FIPS-validated cryptographic modules. Key FIPS features include:

• FIPS-validated OpenSSL provider - Uses OpenSSL FIPS provider for cryptographic operations
• Approved algorithms only - Restricted to FIPS-approved cryptographic algorithms
• FIPS mode enforcement - Cryptographic operations automatically use FIPS-validated modules

Documentation and Resources

• SAP BTP Service Operator GitHub
• Usage documentation

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.