Chainguard Container for karma-fips

A dashboard for managing alerts from Alertmanager

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/karma-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

karma is comparable to the upstream karma image, with the following differences:

• Like all other Chainguard Images, karma features a stripped down, minimal design
• This base image comes with apk and BusyBox and reports as being a Chainguard image.
• It has few-to-zero CVEs
• It does not run as the root user

Most importantly, the karma image contains the OpenSSL FIPS Provider Module (CMVP #4282).

About FIPS Images

FIPS (short for Federal Information Processing Standards) are standards developed by the National Institute of Standards and Technology (NIST) in accordance with the Federal Information Security Management Act (FISMA) and approved by the Secretary of Commerce. FIPS compliance ensures that cryptographic security services within applications meet strict security and integrity standards, and are implemented and configured correctly.

Chainguard offers a variety of language-specific FIPS Images configured out of the box for FIPS development in a given language. We also offer a number base FIPS images for specific applications, such as PostgreSQL, Elasticsearch, and nginx.

Be aware that if you run apk add to install a package onto a Chainguard FIPS Image, there's no guarantee that these packages will function properly; they may throw errors if the package has certain dependencies that aren't available in the image. Additionally, even if they do function properly there's no guarantee that added packages will use FIPS-validated cryptography.

Please refer to Chainguard's FIPS Commitment for more information.

Getting Started

Karma is dashboard for managing alerts from AlertManager. Karma requires an alertmanager instance to be available. Both Karma and AlertManager requires config files. The following is an example altertmanager.yaml confguration file:

alermanager.yaml

global:
  resolve_timeout: 30s
route:
group_by: ["alertname"]
group_wait: 5s
group_interval: 10s
repeat_interval: 999h
receiver: "default"
routes:
  - receiver: "default"
    group_by: []
    match_re:
      alertname: .*
    continue: true
  - receiver: "pagination"
    group_by: ["alertname", "instance"]
    match_re:
      alertname: Pagination Test
    continue: false
  - receiver: "by-cluster-service"
    group_by: ["alertname", "cluster", "service"]
    match_re:
      alertname: .*
    continue: true
  - receiver: "by-name"
    group_by: [alertname]
    match_re:
      alertname: .*
    continue: true
  - receiver: "by-cluster"
    group_by: [cluster]
    match_re:
      alertname: .*
    continue: true

inhibit_rules:
  - source_match:
      severity: "critical"
    target_match:
      severity: "warning"
    # Apply inhibition if the alertname and cluster is the same in both
    equal: ["alertname", "cluster"]
receivers:
  - name: "default"
  - name: "pagination"
  - name: "by-cluster-service"
  - name: "by-name"
  - name: "by-cluster"

More information can be found in the Karma configuration documentation.

To test out this image, deploy a prometheus alertmanager image:

docker run -d \
    --rm \
    --network karma \
    --name prom \
    -p 9093:9093 \
    -v /alertmanager.yaml:/etc/alertmanager/alertmanager.yml \
    cgr.dev/<ORGANISATION>/prometheus-alertmanager:latest

Start a karma container by running the command below

docker run -d \
    --rm \
    --network karma \
    --name karma \
    -p 8083:8080 -e ALERTMANAGER_URI=http://prom:9093/ \
    -v /acls.yaml:/etc/acls.yaml -v /karma.yaml:/etc/karma.yaml \
    cgr.dev/<ORGANISATION>/karma:latest

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.