-
Problem report
-
Resolution: Fixed
-
Trivial
-
6.0.15, 6.4.1, 7.0.0alpha1
-
Sprint 99 (Apr 2023)
-
1
Currently we have deprecated ports and schemas for Controller Manager and Scheduler cluster components in these templates:
- Kubernetes Controller manager by HTTP
- Kubernetes Scheduler by HTTP
- Kubernetes cluster state by HTTP
Following changes should be made:
- {$KUBE.CONTROLLER_MANAGER.PORT}: 10252 -> 10257
- {$KUBE.CONTROLLER_MANAGER.SCHEME}: http -> https
- {$KUBE.CONTROLLER.SERVER.URL}: http://localhost:10252/metrics -> https://localhost:10257/metrics
- {$KUBE.SCHEDULER.PORT}: 10251 -> 10259
- {$KUBE.SCHEDULER.SCHEME}: http -> https
- {$KUBE.SCHEDULER.SERVER.URL}: http://localhost:10251/metrics -> https://localhost:10259/metrics
Also it should be noted in READMEs, that setting up --bind-address option for Scheduler and Controller Manager components might be required, so that Zabbix proxy would be able to reach them.