You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metrics from the brupop-controller-server.brupop-bottlerocket-aws service on the /metrics route are not scrapable on IPv6 clusters. I would expect this endpoint to also work on IPv6 clusters as it does in IPv4 clusters. This prevents our recommended prometheus scrape config from working on IPv6 and blocks users on IPv6 clusters from getting brupop metrics.
In the happy path, getting metrics on an IPv4 cluster:
$ curl brupop-controller-server.brupop-bottlerocket-aws/metrics
# HELP brupop_hosts_state Brupop host's state
# TYPE brupop_hosts_state gauge
brupop_hosts_state{state="Idle"} 2
brupop_hosts_state{state="StagedAndPerformedUpdate"} 1
# HELP brupop_hosts_version Brupop host's bottlerocket version
# TYPE brupop_hosts_version gauge
brupop_hosts_version{bottlerocket_version="1.9.0"} 3
Replication steps:
On an IPv6 cluster running bottlerocket nodes, deploy the brupop stack:
# curl brupop-controller-server.brupop-bottlerocket-aws/metrics
curl: (7) Failed to connect to brupop-controller-server.brupop-bottlerocket-aws port 80 after 1 ms: Connection refused
The fully qualified service also doesn't work:
# curl brupop-controller-server.brupop-bottlerocket-aws.svc.cluster.local/metrics
curl: (7) Failed to connect to brupop-controller-server.brupop-bottlerocket-aws.svc.cluster.local port 80 after 4 ms: Connection refused
And it doesn't seem to be a problem with routing to the service: the nslookup to the service resolves correctly:
Image I'm using:
Issue or Feature Request:
Metrics from the
brupop-controller-server.brupop-bottlerocket-aws
service on the/metrics
route are not scrapable on IPv6 clusters. I would expect this endpoint to also work on IPv6 clusters as it does in IPv4 clusters. This prevents our recommended prometheus scrape config from working on IPv6 and blocks users on IPv6 clusters from getting brupop metrics.In the happy path, getting metrics on an IPv4 cluster:
Replication steps:
brupop-bottlerocket-aws
namespace:The fully qualified service also doesn't work:
And it doesn't seem to be a problem with routing to the service: the
nslookup
to the service resolves correctly:The text was updated successfully, but these errors were encountered: