Open Leeeuijooo opened 5 months ago
+1 level=warn ts=2024-08-26T12:59:54.066715957Z caller=klog.go:106 component=k8s_client_runtime func=Warning msg="spec.template.spec.containers[1].ports[0]: duplicate port definition with spec.template.spec.initContainers[0].ports[0]" level=info ts=2024-08-26T12:59:54.067500703Z caller=operator.go:572 component=alertmanager-controller key=monitoring2/prom-kube-prometheus-stack-alertmanager msg="sync alertmanager" level=info ts=2024-08-26T12:59:54.097428357Z caller=operator.go:982 component=prometheusagent-controller msg="we are gonna check if it Matches" level=info ts=2024-08-26T12:59:54.100686912Z caller=operator.go:766 component=prometheus-controller key=monitoring2/prom-kube-prometheus-stack-prometheus msg="sync prometheus"
Describe the bug a clear and concise description of what the bug is.
msg="http: TLS handshake error from 10.0.226.54:36916: remote error: tls: bad certificate"
What's your helm version?
3.14.2
What's your kubectl version?
1.29.2
Which chart?
kube-prometheus-stack
What's the chart version?
latest
What happened?
I'm Deploying kube-prometheus-stack with ArgoCD Application using Amazon EKS
However, after deploying kube-prometheus-stack, the following error occurred in the prometheus-stack-kube-prom-operator pod.
What you expected to happen?
When I connect to the domain, I am connected to the prometheus server and connected via 302 redirect to the /graph path. However, a 404 error occurs on the redirected page.
How to reproduce it?
The IP (10.0.226.54) is an IP that does not exist in the EKS resource. In my opinion, it looks like the IP came in as NAT from an external source (client).
Also, it says that the tls-ca.crt file does not exist. Is there a way to create it or solve this problem?
Currently, one ALB is set up as Ingress on the Grafana and Prometheus servers.
Below is part of the values.yaml file for the prometheus-stack chart.
Enter the changed values of values.yaml?
Enter the command that you execute and failing/misfunctioning.
I'm Deploying kube-prometheus-stack with ArgoCD using Amazon EKS
Anything else we need to know?
There is my EKS Resources