Downgrade k8s-dqlite (1.4.0 -> 1.3.0 and microcluster) #1044
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We decided not to downgrade k8s-dqlite but instead wait for a fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A recent k8s-dqlite PR (canonical/k8s-dqlite#212) seems to have introduced a regression. The kubelet service is now missing pod events and cilium hangs in "PodScheduled" state.
We'll switch back to k8s-dqlite 1.3.0 for now.
Note that the microcluster dependency has to be downgraded as well, otherwise we're hitting panics.