Control: CronJob containers should have readiness probe
Description
Containers in CronJob definition should have readiness probe. The readiness probes in turn also check dependencies like database connections or other services your container is depending on to fulfill its work.
Usage
Run the control in your terminal:
powerpipe control run kubernetes_compliance.control.cronjob_container_readiness_probeSnapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run kubernetes_compliance.control.cronjob_container_readiness_probe --shareSQL
This control uses a named query:
select coalesce(uid, concat(path, ':', start_line)) as resource, case when c -> 'readinessProbe' is not null then 'ok' else 'alarm' end as status, case when c -> 'readinessProbe' is not null then c ->> 'name' || ' has readiness probe.' else c ->> 'name' || ' does not have readiness probe.' end as reason, name as cronjob_name , coalesce(context_name, '') as context_name, namespace, source_type, coalesce(path || ':' || start_line || '-' || end_line, '') as pathfrom kubernetes_cronjob, jsonb_array_elements(job_template -> 'spec' -> 'template' -> 'spec' -> 'containers') as c;