Skip to main content

RKE2 cluster (host-level)

v0.2.0

RKE2-specific host introspection that kubectl can't give you — embedded-etcd live health (etcdctl endpoint health/status) and snapshot history, node certificate expiry, and the RKE2-bundled containerd via crictl (containers, pods, images). Runs on an RKE2 server node. Generic Kubernetes API reads are in the kubernetes pack; rke2-server / rke2-agent unit status and logs are covered by the linux-core / systemd-deep packs (systemctl status rke2-server, journalctl -u rke2-server).

6 allowed by default
Pack ID
rke2
Vendor
emisar
OS
linux
Actions
6
Required binaries. Install these on the host before relying on the pack — an action that calls a missing one fails at run time.
rke2

Install

emisar pack install validates the pack and verifies its content hash before copying it into /etc/emisar/packs. The --hash below pins the install to the exact bytes on this page — a tampered copy is rejected. After install, reload the runner; it re-reads the catalog and advertises every action.

content hash: sha256:1809a6aea4df6f03697ee022e66473b67593e7d2329fe7f6baf3bc54cc683926

on the runner host
sudo emisar pack install rke2 \
  --hash sha256:1809a6aea4df6f03697ee022e66473b67593e7d2329fe7f6baf3bc54cc683926 \
  --dest /etc/emisar/packs

# Reload so the runner re-reads the catalog:
sudo systemctl reload emisar

Actions 6 total

View on GitHub