Chainguard Container for fluentd-kubernetes-daemonset-fips

Wolfi-based images that provide Fluentd DaemonSets for Kubernetes.

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/fluentd-kubernetes-daemonset-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

Currently, Chainguard only provides an image for the Kinesis DaemonSet. Images for other DaemonSets are not currently provided, but may be requested.

The Chainguard Fluentd Kubernetes DaemonSet Images are comparable to the official Fluentd Kubernetes DaemonSet Images from Docker Hub. However, the Chainguard images contain only the minimum set of tools and dependencies needed to function; for example, they do not include a package manager. Unlike many other Chainguard images, though, these images include a shell.

Getting Started

Kinesis DaemonSet

Create a new Kinesis stream in the AWS Management Console or using the AWS CLI by following the AWS documentation.

Deployment

cat > values.yaml <<EOF
variant: kinesis

image:
  repository: "cgr.dev/ORGANIZATION/fluentd-kubernetes-daemonset-fips"
  pullPolicy: "Always"
  tag: "latest"

env:
  - name: K8S_NODE_NAME
    valueFrom:
      fieldRef:
        fieldPath: spec.nodeName
  - name: AWS_REGION
    value: "<AWS_REGION>"
  - name: AWS_ACCESS_KEY_ID
    value: "<AWS_ACCESS_KEY_ID>"
  - name: AWS_SECRET_ACCESS_KEY
    value: "<AWS_SECRET_ACCESS_KEY>"
  - name: AWS_PROFILE
    value: "<AWS_PROFILE>"
  - name: AWS_SESSION_TOKEN
    value: "<AWS_SESSION>"

fileConfigs:
  00_system.conf: |
    <system>
      log_level debug
    </system>
  04_outputs.conf: |
    <label @OUTPUT>
      <match **>
        @type kinesis_streams
        @id out_kinesis_streams
        endpoint https://<ENDPOINT>
        region <REGION>
        stream_name <STREAM_NAME>
    </label>
EOF

Replace the placeholder values with your AWS credentials and the Kinesis stream details, including the endpoint, region, and stream name.

Deploy the Fluentd Helm Chart with the provided values.yaml file:

helm repo add fluent https://fluent.github.io/helm-charts
helm repo update
helm install fluentd fluent/fluentd -f values.yaml

After a while, you should be see the [DEBUG] log in the fluentd Pods, indicating that the logs are being sent to the Kinesis stream:

$ kubectl logs daemonsets/fluentd

...
[debug]: #0 [out_kinesis_streams] fluentd-kubernetes-daemonset-test: Write chunk 62a9515075decf841a1cb6f2a29d21ef /  67 records /   40 KB
[debug]: #0 [out_kinesis_streams] fluentd-kubernetes-daemonset-test: Finish writing chunk
...

Finally, check the Kinesis records using the AWS Management Console or the AWS CLI:

aws --endpoint-url=https://<ENDPOINT> kinesis get-records \
  --shard-iterator "$(
    aws --endpoint-url=https://<ENDPOINT> \
      kinesis get-shard-iterator \
      --shard-iterator-type TRIM_HORIZON \
      --shard-id shardId-000000000000 \
      --stream-name <STREAM_NAME> \
      --query 'ShardIterator' \
      --output text
  )"

Documentation and Resources

Refer to the official documentation on the Fluentd DaemonSets for Kubernetes for further guidance on setup and configuration.

• Fluentd + Kubernetes documentation
• Fluentd Stream Processing with Kinesis

Image Tagging

This image supports multiple Ruby versions and produces image tags in the following format:

cgr.dev/ORGANIZATION/fluentd-kubernetes-daemonset:<fluentd-version>-<component>-rb<ruby-version>

At present, this image only supports kinesis component with Ruby starting from version 3.1.x to 3.4.x.

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.