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

[Release-1.27] - Expose RKE2 metrics via supervisor port #6092

Closed
brandond opened this issue Jun 1, 2024 · 3 comments
Closed

[Release-1.27] - Expose RKE2 metrics via supervisor port #6092

brandond opened this issue Jun 1, 2024 · 3 comments
Assignees

Comments

@brandond
Copy link
Member

brandond commented Jun 1, 2024

Backport fix for Expose RKE2 metrics via supervisor port

@brandond
Copy link
Member Author

agents are listening on the wrong port, see #5786 (comment)

If we get another 1.27 release in July we can fix it.

@brandond brandond modified the milestones: v1.27.15+rke2r1, Backlog Jun 13, 2024
@brandond
Copy link
Member Author

this is breaking the embedded registry mirror on agents too... so it'll need to be fixed this release.

@aganesh-suse
Copy link

Validated on release-1.27 branch with commit 180bd1e

Environment Details

Infrastructure

  • Cloud
  • Hosted

Node(s) CPU architecture, OS, and Version:

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"

$ uname -m
x86_64

Cluster Configuration:

HA : 3 server / 1 agent

Config.yaml:

Server Node Configs:

token: xxxx
write-kubeconfig-mode: "0644"
node-external-ip: 1.1.1.1
enable-pprof: true
supervisor-metrics: true

Agent node configs:

token: xxxx
node-external-ip: 1.1.1.2
server: https://<server ip>:9345
enable-pprof: true

Testing Steps

  1. Copy config.yaml
$ sudo mkdir -p /etc/rancher/rke2 && sudo cp config.yaml /etc/rancher/rke2
  1. Install RKE2
curl -sfL https://get.rke2.io | sudo INSTALL_RKE2_COMMIT='180bd1e2dec6eeed9e415ee68f6e509b28c46f66' INSTALL_RKE2_TYPE='server' INSTALL_RKE2_METHOD=tar sh -
  1. Start the RKE2 service
$ sudo systemctl enable --now rke2-server
or 
$ sudo systemctl enable --now rke2-agent
  1. Verify Cluster Status:
kubectl get nodes -o wide
kubectl get pods -A
  1. Verify with server and agent IPs for the curl urls on a server node:
curl -vks --cert /var/lib/rancher/k3s/server/tls/client-admin.crt --key /var/lib/rancher/k3s/server/tls/client-admin.key https://<server|agent ip>:6443/metrics
curl -vks --cert /var/lib/rancher/k3s/server/tls/client-admin.crt --key /var/lib/rancher/k3s/server/tls/client-admin.key https://<server|agent ip>:6443/debug/pprof

Validation Results:

  • rke2 version used for validation:
$ rke2 -v
rke2 version v1.27.15-rc3+rke2r1 (180bd1e2dec6eeed9e415ee68f6e509b28c46f66)
go version go1.21.11 X:boringcrypto

Verified that querying all server/agent nodes works (Not providing output due to large size):

sudo curl -vks --cert /var/lib/rancher/rke2/server/tls/client-admin.crt --key /var/lib/rancher/rke2/server/tls/client-admin.key https://<server_node_ip>:9345/debug/pprof/ 

sudo curl -vks --cert /var/lib/rancher/rke2/server/tls/client-admin.crt --key /var/lib/rancher/rke2/server/tls/client-admin.key https://<server_node_ip>:9345/metrics 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants