victorious-analyst-3332
05/18/2022, 2:03 PMkube-controller-manager
metrics on port 10252 are not exposed in RKE2 deployments. We are currently testing v1.22.9+rke2r2
deployed via Rancher v2.6.5
and are seeing the following differences from RKE deployments. Thanks a lot.
RKE cluster:
# netstat -tulpn | grep kube-contro
tcp6 0 0 :::10252 :::* LISTEN 17396/kube-controll
tcp6 0 0 :::10257 :::* LISTEN 17396/kube-controll
RKE2 cluster:
# netstat -tulpn | grep kube-contro
tcp 0 0 127.0.0.1:10257 0.0.0.0:* LISTEN 39961/kube-controll
creamy-pencil-82913
05/18/2022, 5:29 PMvictorious-analyst-3332
05/18/2022, 5:30 PMmetrics-bind-address=0.0.0.0:10249
under kube-proxy-arg
, but I didn’t see a similar arg upstream for kube-controller-managercreamy-pencil-82913
05/18/2022, 5:31 PMvictorious-analyst-3332
05/18/2022, 5:40 PMcreamy-pencil-82913
05/18/2022, 8:30 PMvictorious-analyst-3332
05/18/2022, 9:25 PMrapid-helmet-86074
05/19/2022, 2:25 PM