Skip to content

Commit 48e70ea

Browse files
committed
changed headings
1 parent 21aca5b commit 48e70ea

File tree

1 file changed

+7
-7
lines changed
  • docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/kubernetes

1 file changed

+7
-7
lines changed

docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/kubernetes/advanced.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ For more information how to use the `crdsToDiscover` parameter, please refer to
138138

139139
The K8s exporter supports configuration options to control access to environment variables within JQ queries used in resource mappings.
140140

141-
### `allowAllEnvironmentVariablesInJQ`
141+
<h3> `allowAllEnvironmentVariablesInJQ` </h3>
142142

143143
The `allowAllEnvironmentVariablesInJQ` parameter controls whether all environment variables are accessible in JQ queries.
144144

@@ -148,26 +148,26 @@ The `allowAllEnvironmentVariablesInJQ` parameter controls whether all environmen
148148
:::warning Security Risk
149149
Setting `allowAllEnvironmentVariablesInJQ` to `true` can expose sensitive environment variables to JQ queries. This includes:
150150
- Port credentials (`PORT_CLIENT_ID`, `PORT_CLIENT_SECRET`)
151-
- Kubernetes service account tokens
152-
- Any other environment variables injected into the pod
153-
- Secrets mounted as environment variables
151+
- Kubernetes service account tokens.
152+
- Any other environment variables injected into the pod.
153+
- Secrets mounted as environment variables.
154154

155155
Due to the potential security implication, if you have a need to limit the exposure of environment variables in the exporter's JQ, please set this parameter to `false` and explicitly specify the variables that need to be accessed using JQ through the `allowedEnvironmentVariablesInJQ` parameter.
156156
:::
157157

158-
### `allowedEnvironmentVariablesInJQ`
158+
<h3> `allowedEnvironmentVariablesInJQ` </h3>
159159

160160
The `allowedEnvironmentVariablesInJQ` parameter specifies which environment variables are allowed in JQ queries when `allowAllEnvironmentVariablesInJQ` is set to `false`. This parameter accepts a list of JQ expressions that evaluate to environment variable names or patterns.
161161

162162
Each entry in the list is a JQ expression that should return:
163163
- A specific environment variable name (e.g., `"CLUSTER_NAME"`)
164164
- A pattern for matching multiple variables (e.g., `"^CLUSTER_"` to match all cluster-related environment variables)
165-
- An array of environment variable names or patterns
165+
- An array of environment variable names or patterns.
166166

167167
- **Default value**: `^PORT_, CLUSTER_NAME`
168168
- **Use case**: Restrict access to only specific, safe environment variables in JQ queries for enhanced security. Use JQ expressions to dynamically determine which environment variables should be accessible.
169169

170-
#### Configuration Example
170+
<h3> Configuration Example </h3>
171171

172172
```yaml
173173
allowAllEnvironmentVariablesInJQ: false

0 commit comments

Comments
 (0)