Urgent.News

What's breaking now, across thousands of outlets.

Tech

Kyverno CLI and conftest in CI vs Kyverno at admission

Kapitan compiles an inventory into plain YAML under compiled/ . The registry's compile diff action shows a reviewer what a pull request changes in that YAML. It does not say whether the change is allowed. A container that runs privileged or an image on the tag latest is one line in the diff, and Kapitan compiles it without an error. Kyverno as an admission controller can reject such an object…

The Kyverno CLI and conftest are both used in CI pipelines to check policies against compiled YAML files generated by Kapitan. The Kyverno CLI checks policy compliance on the compiled objects, while conftest runs Rego rules against those objects. Both tools run on two targets: one compliant and one noncompliant.

The compliant target specifies a Deployment with a restricted security profile, including using a non-root user, a default seccomp profile, no privilege escalation, and resource requests and limits. This target passes all 18 policy checks and exits with a 0 status code.

The noncompliant target, however, specifies a Deployment with a non-compliant security profile, including using the latest image tag, no resource requests or limits, and a privileged container. This target fails all 18 policy checks, with each policy providing a failure message. The Kyverno CLI exits with a 1 status code, indicating a failure.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Papra document sharing crosses organization and instance boundaries

Papra document sharing crosses organization and instance boundaries Papra is a self-hosted document archiving platform organized around users, organizations, documents, custom properties, API keys…

  • Papra is a self-hosted document archiving platform for private or organization-wide use.
  • November 21, 2026 search returned 26 index matches for Papra instances.
  • Security measures include TLS deployment, private networks, and tested deletion/recovery process.

Why Running the yes Command Didn't Max Out CPU Usage

Introduction I needed to generate CPU load on a Linux server for testing purposes. Looking for a quick solution, I executed the yes command like this: yes > /dev/null The yes command continuously…

  • Yes command runs infinitely, not maxing CPU usage
  • Single-threaded process limits to one CPU core
  • Overall CPU usage split between cores, not full utilization

More from Friday 20 November →