-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prometheus-kube-prometheus-stack-prometheus-0 & alertmanager-kube-prometheus-stack-alertmanager-0 fails because CA is not trusted #1187
Comments
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 6, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 7, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 9, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 14, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 14, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 14, 2024
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
May 21, 2024
@mnaser Can you also take this into account when you work at the framework for ACME. mpiscaer@a8c75d7 just skips the validation. I would be great if it is able to use the private signed CA to validate. |
mpiscaer
added a commit
to mpiscaer/atmosphere
that referenced
this issue
Jun 8, 2024
vexxhost-bot
pushed a commit
to vexxhost-bot/atmosphere
that referenced
this issue
Jun 11, 2024
vexxhost-bot
pushed a commit
to vexxhost-bot/atmosphere
that referenced
this issue
Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The pods for alertmanager-kube-prometheus-stack-alertmanager-0 & alertmanager-kube-prometheus-stack-alertmanager-0 get into CrashLoopBackOff because of that the CA is not trusted. This CA is selfsigned.
The text was updated successfully, but these errors were encountered: