​
DirectorySecurity Advisories
Sign In
Directory
victoriametrics-vmselect-fips logoFIPS

victoriametrics-vmselect-fips

Last changed

Sign In for Updates

Get notified of upcoming product changes, critical vulnerability notifications and patches and more.

Sign In
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for victoriametrics-fips

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/victoriametrics-fips:latest

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

VictoriaMetrics (Fips) can be deployed as a single node (all image tags without a "-cluster" suffix) or as a distributed cluster. See the github repository for reference: https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master as well as their public facing documentation: https://docs.victoriametrics.com/

In clustered mode, the VictoriaMetrics application itself is broken into 3 different services:

  • vmstorage - stores the raw data and returns the queried data on the given time range for the given label filters
  • vminsert - accepts the ingested data and spreads it among vmstorage nodes according to consistent hashing over metric name and all its labels
  • vmselect - performs incoming queries by fetching the needed data from all the configured vmstorage nodes

This image group also contains several standalone services (that DO vary between clustered and single mode):

  • vmagent - A lightweight metrics collection agent.
  • vmauth - A service that provides authentication and authorization for VictoriaMetrics services. It acts as HTTP proxy, which can authorize, route and load balance requests across VictoriaMetrics components or any other HTTP backends.

Usage

You can install the VictoriaMetrics components using Helm. Below are the Helm install commands for each component:

Install vmagent

helm install vmagent victoria-metrics-agent --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victoriametrics \
  --set image.repository=cgr.dev/chainguard-private/victoriametrics-vmagent-fips \
  --set image.tag=latest

Install vmauth

helm install vmauth victoria-metrics-auth --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victoriametrics \
  --set image.repository=cgr.dev/chainguard-private/victoriametrics-vmauth-fips \
  --set image.tag=latest

Note: You will need to set the config and for sample testing purpose, you can take inspiration from this example:

cat <<YAML | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
metadata:
  name: vmauth-config
  namespace: victoriametrics
data:
  auth.yml: |
    users:
      - username: "user1"
        password: "pass1"
        url_prefix: "http://localhost:8428/"
      - username: "user2"
        password: "pass2"
        url_prefix: "http://localhost:8429/"
    unauthorized_user:
      url_prefix: "http://localhost:8428/"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: vmauth
  namespace: victoriametrics
spec:
  selector:
    matchLabels:
      app: vmauth
  template:
    metadata:
      labels:
        app: vmauth
    spec:
      containers:
      - name: vmauth
        image: cgr.dev/chainguard-private/victoriametrics-vmauth-fips:latest
        args:
          - "-auth.config=/config/auth.yml"
        ports:
        - containerPort: 8427
        volumeMounts:
        - name: vmauth-config
          mountPath: /config
      volumes:
      - name: vmauth-config
        configMap:
          name: vmauth-config
YAML

Install vminsert, vmselect, vmstorage

helm install vminsert victoria-metrics-cluster --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victoriametrics-cluster \
  --set vminsert.image.repository=cgr.dev/chainguard-private/victoriametrics-vminsert-fips \
  --set vminsert.image.tag=latest \
  --set vminsert.image.variant="" \ 
  --set vmselect.image.repository=cgr.dev/chainguard-private/victoriametrics-vmselect-fips \
  --set vmselect.image.tag=latest \
  --set vmselect.image.variant="" \ 
  --set vmstorage.image.repository=cgr.dev/chainguard-private/victoriametrics-vmstorage-fips \
  --set vmstorage.image.tag=latest \
  --set vmstorage.image.variant=""

Note: We use vmstorage.image.variant="" because our images are alredy coming with cluster suffix, so we no longer need to specify it. For further reference, refer to official docs

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:

  • Apache-2.0

  • GCC-exception-3.1

  • GPL-3.0-or-later

  • LGPL-2.1-or-later

  • MIT

  • MPL-2.0

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

This is a FIPS validated image for FedRAMP compliance.

This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.

Learn more about STIGsGet started with STIGs

Related images

Category
FIPS
STIG

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images