Shulou(Shulou.com)05/31 Report--

This article will explain in detail what kube-prometheus NodePort config is like. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

1. After the installation of the default settings is completed, the ports of several main services are not exposed and can only be accessed in localhost. It may be because of security considerations that this strategy is in place. In the test system, NodePort settings can be used as appropriate.

# kubectl-n monitoring get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT (S) AGEalertmanager-main ClusterIP 192.168.74.123 9093/TCP 8halertmanager-operated ClusterIP None 9093/TCP 6783/TCP 8hgrafana ClusterIP 192.168.228.214 3000/TCP 8hkube-state-metrics ClusterIP None 8443/TCP 9443/TCP 8hnode-exporter ClusterIP None 9100/TCP 8hprometheus-adapter ClusterIP 192.168.216.149 443/TCP 8hprometheus-k8s ClusterIP 192.168.109.239 9090/TCP 8hprometheus-operated ClusterIP None 9090/TCP 8hprometheus-operator ClusterIP None 8080/TCP 8h

two。 Modify settin

Configuration file path kube-prometheus-0.1.0/manifests/

Sed-I "12a\ nodePort: 30300" grafana-service.yamlsed-I "13a\\ type:\ NodePort" grafana-service.yamlsed-I "12a\ nodePort: 30090" prometheus-service.yamlsed-I "13a\ type:\ NodePort" prometheus-service.yamlsed-I "12a\ nodePort: 30093" alertmanager-service.yamlsed-I "13a\ type:\ NodePort" alertmanager-service.yaml

3. After re-application, the output of the service port is as follows:

# kubectl-n monitoring get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT (S) AGEalertmanager-main NodePort 192.168.10.137 9093:30093/TCP 12s

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.