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.

Sign up for GitHub

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

Jump to bottom

*: document TLS reload, improve error logging (v3.2) #9400

Closed
gyuho opened this issue Mar 8, 2018 · 1 comment
Closed

*: document TLS reload, improve error logging (v3.2) #9400

gyuho opened this issue Mar 8, 2018 · 1 comment
Assignees
@gyuho
Labels
area/tls

Comments

@gyuho
Copy link
Contributor

gyuho commented Mar 8, 2018 •
edited
Loading

ref. coreos/etcd-operator#1727

We spent a few days debugging around this. Issue was client object deletes cert assets after creation, and following handshake fails from TLS reloads. Both server and client didn't see any informational errors. This is a new feature in 3.2. First, error should have been more evident. Second, documentation and change logs should have been more clear-cut.

/cc @hongchaodeng
@gyuho gyuho added the area/tls label Mar 8, 2018
@gyuho gyuho self-assigned this Mar 8, 2018
@gyuho gyuho mentioned this issue Apr 2, 2018
Merged
@gyuho
Copy link
Contributor Author

gyuho commented Apr 2, 2018

v3.4 will have clear error messages around this. Closing via #9518.

@gyuho gyuho closed this as completed Apr 2, 2018
@echlebek echlebek mentioned this issue May 25, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gyuho gyuho

Labels
area/tls
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gyuho