Skip to content
Snippets Groups Projects
Unverified Commit 90148e23 authored by Nitish Jadia's avatar Nitish Jadia Committed by GitHub
Browse files

fix invalid Usage section reference

Replace Usage section reference to Customizing Kube-Prometheus section.
parent 66c625d0
Branches
Tags v0.4.0
No related merge requests found
......@@ -278,7 +278,7 @@ Once updated, just follow the instructions under "Compiling" and "Apply the kube
## Configuration
Jsonnet has the concept of hidden fields. These are fields, that are not going to be rendered in a result. This is used to configure the kube-prometheus components in jsonnet. In the example jsonnet code of the above [Usage section](#Usage), you can see an example of this, where the `namespace` is being configured to be `monitoring`. In order to not override the whole object, use the `+::` construct of jsonnet, to merge objects, this way you can override individual settings, but retain all other settings and defaults.
Jsonnet has the concept of hidden fields. These are fields, that are not going to be rendered in a result. This is used to configure the kube-prometheus components in jsonnet. In the example jsonnet code of the above [Customizing Kube-Prometheus section](#customizing-kube-prometheus), you can see an example of this, where the `namespace` is being configured to be `monitoring`. In order to not override the whole object, use the `+::` construct of jsonnet, to merge objects, this way you can override individual settings, but retain all other settings and defaults.
These are the available fields with their respective default values:
```
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment