This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
Update linkerd to 2.10.2 #1522
Merged
Update linkerd to 2.10.2 #1522
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
surajssd
force-pushed
the
surajssd/update-linkerd-to-2.10
branch
from
13f3530
to
8151010
Compare
|
Something is wrong with the AWS installation, that it does not wait until all the LinkerD pods are up. Meanwhile in Packet it does wait. |
Signed-off-by: Maartje Eyskens <maartje@kinvolk.io>
surajssd
force-pushed
the
surajssd/update-linkerd-to-2.10
branch
from
8151010
to
b710305
Compare
Release Notes: https://github.com/linkerd/linkerd2/blob/main/CHANGES.md#stable-2101 Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
Remove the two deployments `linkerd-tap` and `linkerd-web` since they are not installed by default. Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
surajssd
force-pushed
the
surajssd/update-linkerd-to-2.10
branch
from
b710305
to
d90dd85
Compare
This commit updates the service monitor for linkerd proxies, the existing config was not selecting linkerd proxy containers. Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
surajssd
force-pushed
the
surajssd/update-linkerd-to-2.10
branch
from
d90dd85
to
ae24e2d
Compare
This change installs the Linkerd in HA mode. Linkerd installation in non-HA mode returns immediately thus leading to installation failure of anything after that. This is because the webhook server is not immediately up, thus leading to errors like this: ``` metadata_access_test.go:101: retrying pod creation, failed with: Internal error occurred: failed calling webhook "linkerd-proxy-injector.linkerd.io": Post "https://linkerd-proxy-injector.linkerd.svc:443/?timeout=10s": dial tcp 10.3.4.242:443: connect: connection refused ``` Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
surajssd
force-pushed
the
surajssd/update-linkerd-to-2.10
branch
from
ae24e2d
to
e795e11
Compare
Is this resolved. Might we add a note that on AWS this is expected and known ? |
ipochi
approved these changes
Jul 12, 2021
Yes it was resolved by making the Linkerd control plane HA. |
invidian
added
area/components
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.