Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document config requirement for monitoring on imported AKS clusters #377

Closed
catherineluse opened this issue Jan 19, 2023 · 1 comment
Closed

Comments

@catherineluse
Copy link
Contributor

catherineluse commented Jan 19, 2023

The context of this issue is that it was originally reported as a bug (rancher/dashboard#4658) in monitoring V1. In order for monitoring to work on imported AKS clusters, exporter-kubelets.https had to be set to true in the Helm chart values. I think that that kind of requirement is better addressed in documentation than in a UI change because when the UI injects certain values, it can lead to version incompatibility issues with the chart.

However, I just searched the monitoring helm chart values (https://github.com/rancher/charts/blob/dev-v2.7/charts/rancher-monitoring/100.0.0%2Bup16.6.0/values.yaml) and I didn't immediately see the same config option available for RKE2.

Someone should ask Team 3 the question: for V2 monitoring on imported AKS clusters, does it require the V2 equivalent of exporter-kubelets.https set to true? If so, I would suggest documenting it in the Rancher docs about monitoring and in the monitoring helm chart README.

@brandond
Copy link
Contributor

brandond commented Mar 23, 2023

The monitoring v2 chart has different values than V1. For V2, it looks to me like the equivalent value is kubelet.serviceMonitor.https and it is set to true by default. There is no cluster-specific kubelet section (rke2Kubelet, rkeKubelet or so on), so there should not be anything to configure.

@martyav martyav closed this as completed Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants