Closed Vrtak-CZ closed 2 months ago
Hi @Vrtak-CZ,
Thank you for reporting this issue!
Could you share what version of metrics-server are you running? 🙏 Have you tried different metrics-server version by any chance?
Thanks again for reaching out!
@curusarn i'm running latest it means registry.k8s.io/metrics-server/metrics-server:v0.7.0
Thank you @Vrtak-CZ!
I'm passing this on to the team to reproduce and fix.
I'm following this issue, I can't get the dashboard and metrics to work, the logs are fine.
2024-04-09T13:44:49.925975Z ERROR source{component_kind="source" component_id=better_stack_kubernetes_metrics_nodes component_type=http_client component_name=better_stack_kubernetes_metrics_nodes}: vector::internal_events::http_client_source: HTTP request processing error. url=https://betterstack-logs-metrics-server/apis/metrics.k8s.io/v1beta1/nodes error=CallRequest { source: hyper::Error(Connect, Custom { kind: Other, error: ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }) }) } error_type="request_failed" stage="receiving" internal_log_rate_limit=true
2024-04-09T13:44:49.948495Z WARN source{component_kind="source" component_id=better_stack_kubernetes_metrics_pods component_type=http_client component_name=better_stack_kubernetes_metrics_pods}:http: vector::internal_events::http_client: HTTP error. error=error trying to connect: dns error: failed to lookup address information: Name or service not known error_type="request_failed" stage="processing" internal_log_rate_limit=true
Using this values.yaml and default metric-server:
metrics-server:
enabled: false
vector:
hostNetwork:
enabled: true
customConfig:
sources:
better_stack_kubernetes_logs:
type: kubernetes_logs
extra_label_selector: "app=my-engine"
sinks:
better_stack_http_sink:
auth:
token: <TOKEN>
better_stack_http_metrics_sink:
auth:
token: <TOKEN>
Hi,
I'm trying to use this helm chart to monitor our kubernetes cluster (EKS - v1.28.5-eks-5e0fdde). But pods constantly crashing.
I have tryed to upgrade vector to latest version and looks like it did not help.
logs