Skip to content
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

argo-server manifest missing --secure flag cause ReadinessProbe handshake failed #5412

Closed
book987 opened this issue Mar 16, 2021 · 2 comments
Labels

Comments

@book987
Copy link
Contributor

book987 commented Mar 16, 2021

Summary

According to #5228 , argo-server deployment enable HTTPS probe by default, but does not specify --secure options in args. This cause readiness probe failed with tls: first record does not look like a TLS handshake, deployment argo-server keeps unhealthy.

Diagnostics

What version of Argo Workflows are you running?
v3.0.0-rc6

Readiness probe failed: Get https://xx.xxx.xxx.xxx:2746/: tls: first record does not look like a TLS handshake

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@book987
Copy link
Contributor Author

book987 commented Mar 16, 2021

already fix in #5212 , but not in v3.0.0-rc6, will this pr be picked in next rc? @alexec

@book987 book987 reopened this Mar 16, 2021
@alexec
Copy link
Contributor

alexec commented Mar 16, 2021

#5409

@book987 book987 closed this as completed Mar 17, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants