Fix an issue of zedkube EdgeNodeClusterStatus Miss token
Description
- seen the error during decryption from token, 'Edge Node Certificate get fail', and most likely due to the initial wait for EdgeNodeCerts is not enough. Like the ControllerCert update, we also add this to the EdgeNodeCert update to re-publish the EdgeNodeClusterStatus
PR dependencies
How to test and validate this PR
This is eve-k w/ clustering or zks. Make sure after cluster is configured, the k3s is not stuck in converting to cluster and waiting for EdgeNodeClusterStatus Token.
Changelog notes
Fix an issue of zedkube EdgeNodeClusterStatus Miss token
PR Backports
16.4-stable
Checklist
- [x] I've provided a proper description
- [ ] I've added the proper documentation
- [ ] I've tested my PR on amd64 device
- [ ] I've tested my PR on arm64 device
- [ ] I've written the test verification instructions
- [ ] I've set the proper labels to this PR
For backport PRs (remove it if it's not a backport):
- [ ] I've added a reference link to the original PR
- [ ] PR's title follows the template
And the last but not least:
- [x] I've checked the boxes above, or I've provided a good reason why I didn't check them.
Please, check the boxes above after submitting the PR in interactive mode.
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 28.08%. Comparing base (2281599) to head (5bd99b0).
:warning: Report is 158 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #5492 +/- ##
==========================================
+ Coverage 19.52% 28.08% +8.55%
==========================================
Files 19 19
Lines 3021 2314 -707
==========================================
+ Hits 590 650 +60
+ Misses 2310 1520 -790
- Partials 121 144 +23
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.