Control: CronJob containers should have a memory limit
Description
Containers in a CronJob should have memory limit which restricts the container to use no more than a given amount of user or system memory.
Usage
Run the control in your terminal:
powerpipe control run kubernetes_compliance.control.cronjob_memory_limitSnapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run kubernetes_compliance.control.cronjob_memory_limit --shareSQL
This control uses a named query:
select coalesce(uid, concat(path, ':', start_line)) as resource, case when c -> 'resources' -> 'limits' ->> 'memory' is null then 'alarm' else 'ok' end as status, case when c -> 'resources' -> 'limits' ->> 'memory' is null then c ->> 'name' || ' does not have a memory limit.' else c ->> 'name' || ' has a memory limit of ' || (c -> 'resources' -> 'limits' ->> 'memory') || '.' 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;