Include Kubernetes Cluster Name in Compliance Report Output

[petrobubka]

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

[HugoPBrito]

Hi @petrobubka,

Thanks for creating this issue. We'll add this one to the roadmap as well and work on it as soon as we can.