clustermesh: update etcd version to v3.5.4 #1421
Merged
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
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.
With helm, etcd uses v3.5.4.
There is no reason to separate cilium-cli, so we will match them.
https://github.com/cilium/cilium/blob/e8104547227af8fa53ed197e13f5879957d8297c/install/kubernetes/cilium/values.yaml#L2288
The container image in v3.5.4 of etcd is multi-platform.
I am using EKS, which is a managed control plane, so I am running on amd64.
Therefore, when using EKS, there are many configurations where the control plane is amd64, but the node runs on arm64.
Currently, the
-arm64suffix of etcd only refers to the architecture of the control plane, so it does not cover many usecases.However, upgrading etcd will solve all the problems.
https://quay.io/repository/coreos/etcd?tab=tags&tag=latest