prowler-cloud/prowler

Include Kubernetes Cluster Name in Compliance Report Output

Open

#7,796 opened on May 20, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (8,957 stars) (1,322 forks)batch import
feature-requesthelp wanted

Description

New feature motivation

Currently, Prowler includes a context field in its compliance report when scanning Kubernetes environments. However, when executing Prowler within multiple in-cluster deployments (e.g. via CronJobs), the context field provides limited value, as it doesn't accurately reflect the originating cluster name.

Solution Proposed

Please include ACCOUNT_UID or CLUSTER_NAME field (or similar) in the compliance report output, which can be explicitly set via a flag or automatically detected from environment variable like CLUSTER_NAME) just like this is now works for general output.

Check https://github.com/prowler-cloud/prowler/issues/7542

Describe alternatives you've considered

Additional context

No response

Contributor guide

Tech stack
pythonkubernetes
Domain
cloudsecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of KubernetesFamiliarity with PythonKnowledge of Prowler's output structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the referenced issue #7542 for a similar implementation of ACCOUNT UID. Examine how Prowler currently generates compliance reports and where the context field is populated. Look for environment variable detection patterns (e.g., CLUSTER NAME) in the codebase, likely in the Kubernetes provider or output modules. Implement adding the cluster name to the report output, ensuring tests verify the new field appears correctly.