You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add cluster name and description to CyberArk Discovery and Context snapshot
- Add ClusterName and ClusterDescription fields to Snapshot struct
- Populate these fields from Options in PostDataReadingsWithOptions
- Add clusterName and clusterDescription Helm values and docs
- Populate cluster_id and cluster_description in the rendered configmap
- Update values.schema.json to include descriptions for the new values
- Add ClusterDescription field to pkg/agent Config and CombinedConfig
- Default MachineHub cluster ID from ARK_USERNAME env when not set
- Clarify comments and add TODO about ClusterID vs ClusterName naming
Signed-off-by: Richard Wall <[email protected]>
A human readable name for the cluster where the agent is deployed (optional).
287
+
288
+
This cluster name will be associated with the data that the agent uploads to the Discovery and Context service. If empty (the default), the service account name will be used instead.
289
+
#### **config.clusterDescription** ~ `string`
290
+
> Default value:
291
+
> ```yaml
292
+
> ""
293
+
> ```
294
+
295
+
A short description of the cluster where the agent is deployed (optional).
296
+
297
+
This description will be associated with the data that the agent uploads to the Discovery and Context service. The description should include contact information such as the email address of the cluster administrator, so that any problems and risks identified by the Discovery and Context service can be communicated to the people responsible for the affected secrets.
"description": "A short description of the cluster where the agent is deployed (optional).\n\nThis description will be associated with the data that the agent uploads to the Discovery and Context service. The description should include contact information such as the email address of the cluster administrator, so that any problems and risks identified by the Discovery and Context service can be communicated to the people responsible for the affected secrets.",
128
+
"type": "string"
129
+
},
130
+
"helm-values.config.clusterName": {
131
+
"default": "",
132
+
"description": "A human readable name for the cluster where the agent is deployed (optional).\n\nThis cluster name will be associated with the data that the agent uploads to the Discovery and Context service. If empty (the default), the service account name will be used instead.",
"description": "You can configure the agent to exclude some annotations or labels from being pushed . All Kubernetes objects are affected. The objects are still pushed, but the specified annotations and labels are removed before being pushed.\n\nDots is the only character that needs to be escaped in the regex. Use either double quotes with escaped single quotes or unquoted strings for the regex to avoid YAML parsing issues with `\\.`.\n\nExample: excludeAnnotationKeysRegex: ['^kapp\\.k14s\\.io/original.*']",
0 commit comments