Sign inSign up

phirumseng/knetrahub-pam-connector-runner

By phirumseng

•Updated 14 days ago

KNetraHub PAM connector runner: signed connectors, isolated from the API process.

Image
0

528

phirumseng/knetrahub-pam-connector-runner repository overview

⁠phirumseng/knetrahub-pam-connector-runner

Signed connectors, executed away from the API that serves your sessions.

KNetraHub is a self-hosted IT operations portal: a Docker Swarm console, full-stack monitoring, work management, privileged access management, IP address management and a database workspace, behind one sign-in. This image is one of its sidecars — a job the portal deliberately does not do inside its own process.

šŸ“– Documentation: https://sengphirum.github.io/KNetraHub/documentation⁠


⁠What this image does

Runs PAM connectors - the code that rotates and verifies credentials on a target system - out of process.

⁠How it works

Connector bundles are baked into the image at a read-only path, and each bundle's digest and signature is verified against the control-plane registry before it is loaded. Work arrives from the control plane over the internal network, authenticated with a runner token; the only writable path in the container is a tmpfs.

⁠What it deliberately does not do

No Docker socket, no writable root filesystem, no inbound port. A misbehaving connector is contained here rather than in the API process that holds live sessions.

⁠Deploying it

Part of a stack, not a standalone container. Deploy it with the stack file that owns it:

docker stack deploy -c docker/docker-compose.pam.yml knetrahub

⁠Supported tags

  • latest — the most recent release
  • x.y.z (e.g. 0.1.11) — immutable release versions

Keep this image on the same version as the rest of the stack.

⁠The rest of the stack

⁠License

Proprietary — Ā© Seng Phirum. All rights reserved.

Tag summary

Content type

Image

Digest

sha256:543028f35…

Size

60.8 MB

Last updated

14 days ago

docker pull phirumseng/knetrahub-pam-connector-runner