Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[16.0] Fix issue of zedkube publish Kube Status without token#5393

Merged
rene merged 1 commit into
lf-edge:16.0from
naiming-zededa:naiming-backport-16.0-token
Nov 12, 2025
Merged

[16.0] Fix issue of zedkube publish Kube Status without token#5393
rene merged 1 commit into
lf-edge:16.0from
naiming-zededa:naiming-backport-16.0-token

Conversation

@naiming-zededa

Copy link
Copy Markdown
Contributor

Description

(cherry picked from commit ccdb468)

PR dependencies

How to test and validate this PR

This is to fix a timing issue, it rarely happens. Make sure when converting eve-k from single-node mode into cluster mode,
the EdgeNodeClusterStatus will eventually have the Token advertised.

Changelog notes

Fix issue of zedkube publish Kube Status without token

PR Backports

Checklist

  • 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:

  • I've checked the boxes above, or I've provided a good reason why I didn't
    check them.

- seen an issue of zedkube publishing EdgeNodeClusterStatus w/o the
  Token. Even though we check the controller cert subscription at the
  beginning of the process. Add the re-publish the status upon new
  controller-cert update
- backport PR lf-edge#5368

Signed-off-by: naiming-zededa <[email protected]>
(cherry picked from commit ccdb468)

@eriknordmark eriknordmark left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rene rene merged commit ab27831 into lf-edge:16.0 Nov 12, 2025
44 of 45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants