added new guide for k8s-exporter's jq env vars option

[matan84]

Description

Added new page for configuring env vars restriciton to the k8s-exporter

Added docs pages

Please also include the path for the added docs

• Kubernetes advanced configuration (build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/kubernetes/advanced?current-config-param=jqConfiguration)

[aws-amplify-eu-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2910.d2ngvl90zqbob8.amplifyapp.com

[MPTG94]

Left some small suggestions for better wording.

[MatanHeledPort]

/review

[qodo-merge-pro]

PR Reviewer Guide 🔍

(Review updated until commit 6cc8f4b)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Styling/Consistency Ensure tab label capitalization and terminology match existing docs (e.g., "Kubernetes" vs "K8s", "JQ" vs "jq"); confirm new TabItem value key aligns with sidebar link and anchors. {label: "JQ Configuration", value: "jqConfiguration"}, ]} > <TabItem value="resyncInterval"> Security Wording The warning block is good, but consider consistent product-sensitive examples and neutral phrasing; verify that listing specific secret names does not encourage exposing them and add guidance to use Kubernetes secrets/values files. :::warning Security Risk Setting `allowAllEnvironmentVariablesInJQ` to `true` can expose sensitive environment variables to JQ queries. This includes: - Port credentials (`PORT_CLIENT_ID`, `PORT_CLIENT_SECRET`) - Kubernetes service account tokens - Any other environment variables injected into the pod - Secrets mounted as environment variables Only enable this setting if you trust all JQ queries in your resource mappings and understand the security implications. ::: YAML/CLI Examples Validate quoting/escaping for --set with comma-separated values and arrays; ensure code fences have correct languages and consistent indentation to match CONTRIBUTING style. ```bash --set allowAllEnvironmentVariablesInJQ=true Example 2: Restrict to specific environment variables (recommended) --set allowAllEnvironmentVariablesInJQ=false \ --set allowedEnvironmentVariablesInJQ="CLUSTER_NAME,NAMESPACE,REGION" Example 3: Using values.yaml file allowAllEnvironmentVariablesInJQ: false allowedEnvironmentVariablesInJQ: "CLUSTER_NAME,NAMESPACE,REGION" Example 4: Using patterns to allow groups of variables --set allowAllEnvironmentVariablesInJQ=false \ --set allowedEnvironmentVariablesInJQ="CLUSTER_*,NAMESPACE,REGION_*" This configuration allows: All environment variables starting with CLUSTER_ (e.g., CLUSTER_NAME, CLUSTER_ID) Specific variable: NAMESPACE All environment variables starting with REGION_ (e.g., REGION_US, REGION_EU) Example 5: Using patterns in values.yaml allowAllEnvironmentVariablesInJQ: false allowedEnvironmentVariablesInJQ: "CLUSTER_*,NAMESPACE_*,REGION_*" This configuration allows all environment variables that start with CLUSTER_, NAMESPACE_, or REGION_. </details> </td></tr> </table>

[MatanHeledPort]

/review

[qodo-merge-pro]

Persistent review updated to latest commit 6cc8f4b

[MatanHeledPort]

/review

[qodo-merge-pro]

Persistent review updated to latest commit 6cc8f4b

[kodjomiles]

Looks good some few suggestions