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.
99
Quality
Pending
Does it follow best practices?
Impact
99%
1.19xAverage score across 31 eval scenarios
Pending
The risk profile of this skill
Write a Rego policy in the package kubernetes.namespaces that validates Kubernetes namespace objects. The policy should:
deny contains msg if { ... } for collecting violationsdata.restricted_names — check using input.metadata.name in data.restricted_names (not != restricted_names[_] which is a common bug)"owner" is missing from input.metadata.annotationssprintf with the correct number of arguments matching the format string verbs{
"metadata": {
"name": "production",
"annotations": {
"owner": "platform-team"
}
}
}{
"restricted_names": ["default", "kube-system", "kube-public"]
}production with owner annotation → no violationskube-system → deny (restricted name)owner annotation → deny with annotation name in messagedocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31