Control: ReplicaSet containers argument secure port should not be set to 0
Description
This check ensures that the container in the ReplicaSet has secure port not set to 0.
Usage
Run the control in your terminal:
powerpipe control run kubernetes_compliance.control.replicaset_container_argument_secure_port_not_0
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run kubernetes_compliance.control.replicaset_container_argument_secure_port_not_0 --share
SQL
This control uses a named query:
select coalesce(uid, concat(path, ':', start_line)) as resource, case when (c -> 'command') @> '["kube-apiserver"]' and (c -> 'command') @> '["--secure-port=0"]' then 'alarm' else 'ok' end as status, case when (c -> 'command') @> '["kube-apiserver"]' and (c -> 'command') @> '["--secure-port=0"]' then c ->> 'name' || ' secure port set to 0.' else c ->> 'name' || ' secure port not set to 0.' end as reason, name as replicaset_name , coalesce(context_name, '') as context_name, namespace, source_type, coalesce(path || ':' || start_line || '-' || end_line, '') as pathfrom kubernetes_replicaset, jsonb_array_elements(template -> 'spec' -> 'containers') as c;