prowler-cloud/prowler

Include Kubernetes Cluster Name in Compliance Report Output

Open

#7,796 创建于 2025年5月20日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Python (8,957 star) (1,322 fork)batch import
feature-requesthelp wanted

描述

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

贡献者指南

技术栈
pythonkubernetes
领域
cloudsecurity
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of KubernetesFamiliarity with PythonKnowledge of Prowler's output structure
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
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.
Include Kubernetes Cluster Name in Compliance Report Output · prowler-cloud/prowler#7796 | Good First Issue