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
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?
grafana
...
ingress:
enabled: true
ingressClassName: alb
annotations: {
alb.ingress.kubernetes.io/scheme: internet-facing,
alb.ingress.kubernetes.io/target-type: ip,
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}, {"HTTP":80}]',
alb.ingress.kubernetes.io/certificate-arn: <AWS_CA>,
alb.ingress.kubernetes.io/success-codes: 200-399,
alb.ingress.kubernetes.io/load-balancer-name: monitoring-alb,
alb.ingress.kubernetes.io/ssl-redirect: '443',
alb.ingress.kubernetes.io/group.name: "monitoring"
}
labels: {}
hosts:
- grafana.help.store
## Path for grafana ingress
path: /
## TLS configuration for grafana Ingress
## Secret must be manually created in the namespace
##
tls: []
# - secretName: grafana-general-tls
# hosts:
# - grafana.example.com
# # To make Grafana persistent (Using Statefulset)
# #
persistence:
enabled: true
# type: sts
storageClassName: "gp2"
accessModes:
- ReadWriteOnce
size: 20Gi
------------------------------------------------------------------------------
prometheus
ingress:
enabled: true
ingressClassName: alb
annotations: {
alb.ingress.kubernetes.io/scheme: internet-facing,
alb.ingress.kubernetes.io/target-type: ip,
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}, {"HTTP":80}]',
alb.ingress.kubernetes.io/certificate-arn: <AWS_CA>,
alb.ingress.kubernetes.io/success-codes: 200-399,
alb.ingress.kubernetes.io/load-balancer-name: monitoring-alb,
alb.ingress.kubernetes.io/group.name: "monitoring",
alb.ingress.kubernetes.io/ssl-redirect: '443'
}
labels: {}
## Redirect ingress to an additional defined port on the service
# servicePort: 8081
hosts:
- prometheus.help.store
## Paths to use for ingress rules - one path should match the prometheusSpec.routePrefix
##
paths:
- /
## For Kubernetes >= 1.18 you should specify the pathType (determines how Ingress paths should be matched)
## See https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#better-path-matching-with-path-types
# pathType: ImplementationSpecific
## TLS configuration for Prometheus Ingress
## Secret must be manually created in the namespace
##
tls: []
# - secretName: prometheus-general-tls
# hosts:
# - prometheus.example.com
Enter the command that you execute and failing/misfunctioning.
I'm Deploying kube-prometheus-stack with ArgoCD using Amazon EKS
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
The text was updated successfully, but these errors were encountered: