Host Ipc
k8s.host-ipc
Fails when workload PodSpecs set hostIPC: true. Sharing the host's
IPC namespace exposes node-wide System V IPC and POSIX shared memory
to the container, which can be abused to read or tamper with other
workloads' shared-memory state. Workloads that genuinely need host IPC
can opt out via include/exclude in lunar-config.yml.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Host Ipc with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/k8s@v1.0.5
include: [host-ipc]
# with: ...
How This Guardrail Works
This guardrail is part of the Kubernetes Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
min_replicas
|
Optional |
3
|
Minimum replicas required for HPAs (default 3) |
max_limit_to_request_ratio
|
Optional |
4
|
Maximum ratio of limits to requests for CPU/memory (default 4) |
min_kubectl_version
|
Optional |
1.28
|
Minimum kubectl version required in CI (semver, e.g. "1.28") |
Kubernetes Guardrails
This guardrail is part of the Kubernetes Guardrails policy, which includes 11 guardrails for deployment and infrastructure.
Ready to Automate Your Standards?
See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 200+ built-in guardrails.