-
Notifications
You must be signed in to change notification settings - Fork 165
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
Edge-Node Clustering miscellaneous bug fixes #4549
Edge-Node Clustering miscellaneous bug fixes #4549
Conversation
naiming-zededa
commented
Jan 25, 2025
- handle the ENC App Status and cluster reachable conditions and with error message status
- fix an issue in checkAppsStatus() of using staled oldStatus{}
- in multiple applications case, the there is a bug since now we changed the logic to not always publish the ENClusterAppStatus, need to use the correct oldStatus for the application
- fix the token rotation failure and waitfor cluster status bug and fix a bug in waiting for bootstrap server status, we can fall into the 'else' condition and get a wrong cert
- if not all-pods-ready, not printing the misleading 'applying node labels' message, instead log the 'Not all pods are ready'
- handle the case convert to single-node and immediately back to cluster-mode again. we need towait for the bootstrap 'cluster' status before moving on
- try to fix an issue of 'k3s.log' file rotation not taking effect once a while. the file size can not be truncated. Add a HUP signal before truncate the file
f724b48
to
3107eb9
Compare
3107eb9
to
d89e34f
Compare
d89e34f
to
d9ade52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kick off tests
d9ade52
to
b5364d1
Compare
b5364d1
to
e91485f
Compare
no conflict, but rebased again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
- handle the ENC App Status and cluster reachable conditions and with error message status - fix an issue in checkAppsStatus() of using staled oldStatus{} - in multiple applications case, the there is a bug since now we changed the logic to not always publish the ENClusterAppStatus, need to use the correct oldStatus for the application - fix the token rotation failure and waitfor cluster status bug and fix a bug in waiting for bootstrap server status, we can fall into the 'else' condition and get a wrong cert - if not all-pods-ready, not printing the misleading 'applying node labels' message, instead log the 'Not all pods are ready' - handle the case convert to single-node and immediately back to cluster-mode again. we need towait for the bootstrap 'cluster' status before moving on - try to fix an issue of 'k3s.log' file rotation not taking effect once a while. the file size can not be truncated. Add a HUP signal before truncate the file Signed-off-by: Naiming Shen <naiming@zededa.com>
e91485f
to
5cd695f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM