kafka_exporter, A Real KRaft Broker And An Offset That Moved

kafka_exporter (SHA-256 pinned per architecture) on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test brings up a KRaft broker first (the exporter exits without one), sees kafka_brokers 1, creates a topic, produces three messages and reads the partition's offset at 3. Original role, live-tested on Rocky Linux 10.

ansibleMessaging & Streaming

Verification

Live-tested

Really deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.

Conformance

  • Static validation (yamllint · ansible-lint)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-09-21 · podman 4.9.3 · ansible 2.21.4 · how we verify

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/ansible-kafka-exporter/badge)](https://www.iac-bazaar.com/catalog/ansible-kafka-exporter?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Ansible role 1.0.0, live-tested on IaC Bazaar: [kafka_exporter, A Real KRaft Broker And An Offset That Moved](https://www.iac-bazaar.com/catalog/ansible-kafka-exporter?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```yaml
# kafka_exporter, A Real KRaft Broker And An Offset That Moved: https://www.iac-bazaar.com/catalog/ansible-kafka-exporter (download from your IaC Bazaar account)
```

Preview:IaC Bazaar: live-tested

Documentation

kafka-exporter

kafka_exporter, Kafka topics, partitions, offsets and consumer groups as Prometheus metrics, from the upstream release (SHA-256 pinned per architecture, the release carries no checksum file), as a hardened system service on loopback. Original role for EL 10, live-tested with podman on Rocky Linux 10.

No package, and no checksum file to speak of. EL 10 carries no kafka_exporter, and danielqsj publishes the release with nothing beside it. This role pins the SHA-256 per architecture beside the version, has Ansible's get_url refuse the asset unless it matches, and installs the binaries as root's in /usr/local/bin. A new release is a new pair, on purpose.

A service account, a hardened unit, a loopback listener. kafka_exporter is a system user with no shell that owns the data directory and nothing else; the unit runs with NoNewPrivileges, PrivateTmp, ProtectHome and ProtectSystem=strict. The listener is 127.0.0.1:9308 by default, for a proxy that authenticates or a client on the same host; the live test reads the listening sockets and expects loopback only.

Proven against a real broker. kafka_exporter exits when it cannot reach a broker at start, and the unit restarts it every five seconds until one answers, so the live test brings a KRaft broker up first (Apache's release, its SHA-512 checked, a transient unit), then reads kafka_brokers 1, creates a topic, produces three messages and reads kafka_topic_partition_current_offset{partition="0",topic="lane"} 3. A broker that goes away later is not seen: the exporter keeps its last client, so alert on scrape errors rather than on kafka_brokers. On a real host point kafka_exporter_kafka_server at the Kafka already there (the kafka role in this catalogue).

License

Commercial - IaC Bazaar EULA. (c) IaC Bazaar.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Variables
  • Test

Related modules

Live-tested

ansible-kafka

Apache Kafka 4 (SHA-512 pinned) on Java 21, one KRaft node on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test creates a topic, produces one message, consumes it back and reads the metadata quorum; the metadata log is formatted once as the service user and the root-owned release tree is run in place. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-dovecot

Dovecot from AppStream: IMAP for your mail clients and LMTP for your MTA, Maildir in each home, TLS required before any login, a minimum TLS version checked before it lands, and every listener on loopback until you open it. The live test delivers over LMTP, reads the message over IMAPS, and sees a plaintext login from another address refused. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-gotify

Gotify on EL 10 from the vendor's release, pinned by a SHA-256 the role carries (the vendor publishes no checksum file), as a hardened systemd service on loopback with its settings in an EnvironmentFile; the live test creates an application, pushes a message with its token, reads it back as the admin, and sees a wrong password and a bad token refused. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-postfix-tls

An EL host opens no submission service, so every client sends on port 25 where plaintext is accepted. This role adds 587, which refuses mail until the session is encrypted, and 465, which is TLS from the first byte. Port 25 keeps taking plaintext on purpose and the live test asserts it, because a mail exchanger that demands STARTTLS loses mail. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-mosquitto-broker

Mosquitto (MQTT) with accounts: the package starts in local-only mode with anonymous clients allowed, no persistence directory and no packet-size limit. This role writes a listener that refuses anonymous and wrong-password clients (proved live), keeps retained messages across restarts, caps packets at 1 MiB, and renders topic ACLs from a list. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-nats

nats on EL 10 from the GitHub release; get_url refuses it unless its SHA-256 is in the vendor's checksums file, and the live test re-checks it, then saves a context under a throwaway config home, reads it back, and runs server check connection against a dead port expecting exit 2 and CRITICAL. Pinned. Original role, live-tested on Rocky Linux 10.

View module