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 (1,322 forks)batch import
feature-requesthelp wanted

Repository metrics

Stars
 (8,957 stars)
PR merge metrics
 (Avg merge 9d 17h) (314 merged PRs in 30d)

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

Research direction
Implement a flag or environment variable (e.g., CLUSTER NAME) to include a cluster identifier in compliance report output, following existing patterns in the codebase.
Tech stack
python
Domain
securityinfrastructurecloud
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70