CtrlK
BlogDocsLog inGet started
Tessl Logo

nicholasjackson/opa-rego-language

Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test.

96

1.18x
Quality

94%

Does it follow best practices?

Impact

97%

1.18x

Average score across 32 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-24/

Kubernetes: Common Testing Pattern

Write a Rego admission policy that denies pods containing containers without CPU and memory resource limits set.

Also write a _test.rego file that tests the policy. The test file must be named with the _test.rego suffix, use the _test package suffix, prefix all test functions with test_, mock input using with input as, and include both a passing case (all containers have limits) and a failing case (a container is missing limits).

Input

{
  "request": {
    "kind": {"kind": "Pod"},
    "object": {
      "metadata": {"name": "my-pod"},
      "spec": {
        "containers": [
          {
            "name": "app",
            "resources": {}
          }
        ]
      }
    }
  }
}

Expected behaviour

  • Deny pods where any container is missing resources.limits.cpu or resources.limits.memory
  • Allow pods where all containers have both limits set
  • The deny message should include the container name

README.md

rules.md

tile.json