Having problems using the K8s integration with optscale #694
Replies: 7 comments
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Geraldo155 |
Beta Was this translation helpful? Give feedback.
-
|
I'm so sorry for the delay on answering. I have updated my deployment to the latest versions after some down time and was able to solve this issue on earlier versions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I've been using OptScale with my team for the past couple of weeks and recently started testing the Kubernetes Rightsizing functionality. To do this, I created a cluster and deployed the OptScale pods to monitor cluster data, following the installation steps provided on the Data Sources page using Helm.
However, after deployment, I noticed the following logs from the kube-cost-metrics-collector-prometheus-server pod:
ts=2025-06-25T17:15:13.771Z caller=dedupe.go:112 component=remote level=warn remote_name=optscale url=https://172.31.32.134:26623/storage/api/v2/write msg="Failed to send batch, retrying" err="Post \"https://172.31.32.134:26623/storage/api/v2/write\": http: server gave HTTP response to HTTPS client"The URL I currently use to access the OptScale UI is http://172.31.32.134:26623, so it seems that the Helm chart may have configured an HTTPS endpoint by default, which might be causing the mismatch.
When I updated the target URL in the ConfigMap to use HTTP instead of HTTPS, I got a different error:
ts=2025-06-25T17:11:15.346Z caller=dedupe.go:112 component=remote level=error remote_name=optscale url=http://172.31.32.134:26623/storage/api/v2/write msg="non-recoverable error" count=500 exemplarCount=0 err="server returned HTTP status 404 Not Found: <!DOCTYPE html>"It seems that the /storage/api/v2/write doesn't exist on my deploy, maybe something happened during installation.
Setup:
OptScale is deployed on a VM in AWS that matches the recommended specifications, and the Kubernetes cluster is also running in AWS in the same availability zone.
Exploring:
Trying to understand better why this error happenen I created an account on the optscale website and deploy a minikube cluster on a data source on the official website. But even on the official webiste the pod kube-cost-metrics-collector-prometheus-server-7f87cd848b-mkk85 send this log:
Has anyone experienced a similar issue or have any suggestions for resolving this? Could this be related to a misconfiguration during installation?
Best regards,
Geraldo
Beta Was this translation helpful? Give feedback.
All reactions