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
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,16 @@ go run main.go echo
46
46
The Jetstack-Secure agent exposes its metrics through a Prometheus server, on port 8081.
47
47
The Prometheus server is disabled by default but can be enabled by passing the `--enable-metrics` flag to the agent binary.
48
48
49
+
If you deploy the agent with Helm, using the venafi-kubernetes-agent Helm chart, the metrics server will be enabled by default, on port 8081.
50
+
If you use the Prometheus Operator, you can use `--set metrics.podmonitor.enabled=true` to deploy a `PodMonitor` resource,
51
+
which will add the venafi-kubernetes-agent metrics to your Prometheus server.
52
+
53
+
The following metrics are collected:
54
+
* Go collector: via the [default registry](https://github.com/prometheus/client_golang/blob/34e02e282dc4a3cb55ca6441b489ec182e654d59/prometheus/registry.go#L60-L63) in Prometheus client_golang.
55
+
* Process collector: via the [default registry](https://github.com/prometheus/client_golang/blob/34e02e282dc4a3cb55ca6441b489ec182e654d59/prometheus/registry.go#L60-L63) in Prometheus client_golang.
56
+
* Agent metrics:
57
+
*`data_readings_upload_size`: Data readings upload size (in bytes) sent by the jscp in-cluster agent.
Copy file name to clipboardExpand all lines: deploy/charts/venafi-kubernetes-agent/README.md
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -159,6 +159,15 @@ You should see the following events for your service account:
159
159
| image.repository | string |`"registry.venafi.cloud/venafi-agent/venafi-agent"`| Default to Open Source image repository |
160
160
| image.tag | string |`"v0.1.48"`| Overrides the image tag whose default is the chart appVersion |
161
161
| imagePullSecrets | list |`[]`| Specify image pull credentials if using a private registry example: - name: my-pull-secret |
162
+
| metrics.enabled | bool |`true`| Enable the metrics server. If false, the metrics server will be disabled and the other metrics fields below will be ignored. |
163
+
| metrics.podmonitor.annotations | object |`{}`| Additional annotations to add to the PodMonitor. |
164
+
| metrics.podmonitor.enabled | bool |`false`| Create a PodMonitor to add the metrics to Prometheus, if you are using Prometheus Operator. See https://prometheus-operator.dev/docs/operator/api/#monitoring.coreos.com/v1.PodMonitor|
165
+
| metrics.podmonitor.endpointAdditionalProperties | object |`{}`| EndpointAdditionalProperties allows setting additional properties on the endpoint such as relabelings, metricRelabelings etc. For example: endpointAdditionalProperties: relabelings: - action: replace sourceLabels: - __meta_kubernetes_pod_node_name targetLabel: instance |
| metrics.podmonitor.interval | string |`"60s"`| The interval to scrape metrics. |
168
+
| metrics.podmonitor.labels | object |`{}`| Additional labels to add to the PodMonitor. |
169
+
| metrics.podmonitor.prometheusInstance | string |`"default"`| Specifies the `prometheus` label on the created PodMonitor. This is used when different Prometheus instances have label selectors matching different PodMonitors. |
170
+
| metrics.podmonitor.scrapeTimeout | string |`"30s"`| The timeout before a metrics scrape fails. |
162
171
| nameOverride | string |`""`| Helm default setting to override release name, usually leave blank. |
163
172
| nodeSelector | object |`{}`| Embed YAML for nodeSelector settings, see https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/|
164
173
| podAnnotations | object |`{}`| Additional YAML annotations to add the the pod. |
@@ -172,4 +181,6 @@ You should see the following events for your service account:
172
181
| serviceAccount.create | bool |`true`| Specifies whether a service account should be created |
173
182
| serviceAccount.name | string |`""`| The name of the service account to use. If blank and `serviceAccount.create` is true, a name is generated using the fullname template of the release. |
174
183
| tolerations | list |`[]`| Embed YAML for toleration settings, see https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/|
184
+
| volumeMounts | list |`[]`| Additional volume mounts to add to the Venafi Kubernetes Agent container. This is useful for mounting a custom CA bundle. Any PEM certificate mounted under /etc/ssl/certs will be loaded by the Venafi Kubernetes Agent. For example: volumeMounts: - name: cabundle mountPath: /etc/ssl/certs/cabundle subPath: cabundle readOnly: true |
185
+
| volumes | list |`[]`| Additional volumes to add to the Venafi Kubernetes Agent container. This is useful for mounting a custom CA bundle. For example: volumes: - name: cabundle configMap: name: cabundle optional: false defaultMode: 0644 In order to create the ConfigMap, you can use the following command: kubectl create configmap cabundle \ --from-file=cabundle=./your/custom/ca/bundle.pem |
0 commit comments