owner label is great not only for financial ownership but also useful for operational ownership. Consider adding an
owner label to your workload with the name, email alias or Slack channel of the team responsible for the service. This will make it easier to alert the relevant team or team member when necessary.
Labels' keys and values are case-sensitive!
Targeted objects by this rule (types of
kind): Deployment / Pod / DaemonSet / StatefulSet / ReplicaSet / CronJob / Job
Complexity: easy (What does this mean?)
Policy as code identifier: WORKLOAD_MISSING_LABEL_OWNER_VALUE
This rule will fail
owner key is missing from the
Rule output in the CLI
$ datree test *.yaml
>> File: failExample.yaml
❌ Ensure workload has a configured `owner` label [1 occurrence]
💡 Missing label object `owner` - add a proper owner label to know which person/team to ping when needed
How to fix this failure