Linkerd check failing for ExternalName #9814
-
I recently upgraded Linkerd to 2.12.2 and I'm facing an issue with ExternalName service.
As you may know, ExternalName in Kubernetes doesn't have any IP, so I cannot allow it in the clusterNetworks CIDR. This blocks me to install Linkerd Viz. Anyone else facing this issue? |
Beta Was this translation helpful? Give feedback.
Answered by
mateiidavid
Nov 11, 2022
Replies: 1 comment 2 replies
-
@mhonorio thanks for raising this. We've fixed this, you can check the details in the original issue, #9661 The fix is present in the most recent edge at the time of writing ( |
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
mhonorio
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@mhonorio thanks for raising this. We've fixed this, you can check the details in the original issue, #9661
The fix is present in the most recent edge at the time of writing (
edge-22.10.3
), and will likely be shipped in the nextstable-2.12.3
release.