generated from Cloudzero/template-cloudzero-open-source
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CP-24886: ensure KSM service and KSM target always match (#143)
* CP-24886: ensure ksm svc and target match * Update NOTES.txt --------- Co-authored-by: Thomas Evans <[email protected]>
- Loading branch information
Showing
6 changed files
with
57 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
## [Release 1.0.0-beta-10](https://github.com/Cloudzero/cloudzero-agent/compare/v0.0.28...v1.0.0-beta-10) (2025-01-17) | ||
|
||
This release adds logic to ensure that the static target used in the `env-validator` and in the Prometheus configuration always matches the internal Service created by the `kube-state-metrics` subchart. | ||
|
||
### Upgrade Steps | ||
Upgrade using the following command: | ||
```console | ||
helm upgrade --install <RELEASE_NAME> cloudzero-beta/cloudzero-agent -n <NAMESPACE> --create-namespace -f configuration.example.yaml --version 1.0.0-beta-10 | ||
``` | ||
|
||
### Improvements | ||
* **Static Target and KSM Service Always Match:** Both the `env-validator` and the Prometheus agent require an address for a `kube-state-metrics` Service. By default, the Service name generated by the `kube-state-metrics` subchart generates a name that matches the target value generated by the chart. | ||
|
||
However, if the user overrides the name of the `kube-state-metrics` Service using `kubeStateMetrics.fullnameOverride`, there can be a mismatch between the names. This change attempts to mirror the logic used by the internal `kube-state-metrics` chart so that the target and Service names will match regardless of user input. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
{{- if and .Values.kubeStateMetrics.targetOverride .Values.kubeStateMetrics.enabled }} | ||
*************** | ||
|
||
|
||
****WARNING**** | ||
|
||
This chart has been installed with both `kubeStateMetrics.targetOverride` and `kubeStateMetrics.enabled`. This is almost certainly not a correct configuration. | ||
|
||
The purpose of targetOverride is for you to bring your own kube-state-metrics. If `kubeStateMetrics.enabled` is true, and `kubeStateMetrics.targetOverride` is not null, | ||
it is likely you will not receive the required metrics and data in the CloudZero platform since the agent may be looking for the wrong service address for KSM. | ||
|
||
Please refer to the documentation for guidance on `kubeStateMetrics` settings. | ||
|
||
*************** | ||
{{- end }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters