[node-manager][bashible-apiserver] Fix: no context for node groups in static cluster #571
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If cloud provider does not present in bashible-apiserver input context will not return error for calculating checksum.
In dhctl, first will check deckhouse pod is ready and then will get and print log. It needs for add master node group. Without master node group we can get case in which control-plane manager change kublet tls settings, and dhctl cannot get logs, because kubelet certificate is become not valid.
Deleted
test_data
dir with context render test.Why do we need it, and what problem does it solve?
Static cluster does not bootstrap.
Changelog entries