Failed when follow the multi-cluster communication tutorial #6465
-
|
I am trying to follow the Multi-cluster communication tutorial. Here are my steps: # 1. Generate certificates
cd kubernetes/certificates
step certificate create root.linkerd.cluster.local root.crt root.key --profile=root-ca --no-password --insecure
step certificate create identity.linkerd.cluster.local issuer.crt issuer.key \
--profile=intermediate-ca --not-after=8760h --no-password --insecure \
--ca=root.crt --ca-key=root.key
# 2. Create clusters
cd ../..
# The two kind cluster config files can be found at https://github.com/Hongbo-Miao/hongbomiao.com/tree/b180a8216b0fc4376608553204c3c481d6f58bce/kubernetes/kind
kind create cluster --name=west --config=kubernetes/kind/west-cluster-config.yaml
kind create cluster --name=east --config=kubernetes/kind/east-cluster-config.yaml
# 3. Install Linkerd
linkerd install \
--identity-trust-anchors-file=kubernetes/certificates/root.crt \
--identity-issuer-certificate-file=kubernetes/certificates/issuer.crt \
--identity-issuer-key-file=kubernetes/certificates/issuer.key |
tee \
>(kubectl --context=kind-west apply --filename=-) \
>(kubectl --context=kind-east apply --filename=-)
# 4. Install Ingress
for ctx in kind-west kind-east; do
echo "Installing Ingress on ${ctx}"
VERSION=$(curl https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/stable.txt)
kubectl apply --filename="https://raw.githubusercontent.com/kubernetes/ingress-nginx/${VERSION}/deploy/static/provider/kind/deploy.yaml"
echo "-------------"
done
# 5. Patch Ingress
for ctx in kind-west kind-east; do
echo "Patching Ingress on ${ctx}"
# The two patch files mentioned below can be found at https://github.com/Hongbo-Miao/hongbomiao.com/tree/b180a8216b0fc4376608553204c3c481d6f58bce/kubernetes/patch
# What it does is meshing ingress-nginx-controller, which should be same with running
# kubectl get deployment ingress-nginx-controller -n=ingress-nginx -o=yaml | linkerd inject --ingress - | kubectl apply -f=-
kubectl patch configmap ingress-nginx-controller --namespace=ingress-nginx --patch "$(cat kubernetes/patch/ingress-nginx-controller-configmap-patch.yaml)"
kubectl patch deployment ingress-nginx-controller --namespace=ingress-nginx --patch "$(cat kubernetes/patch/ingress-nginx-controller-deployment-patch.yaml)"
echo "-------------"
done
# 6. Check Linkerd
for ctx in kind-west kind-east; do
echo "Checking cluster: ${ctx}"
linkerd --context=${ctx} check || break
echo "-------------"
done
# 7. Install Linkerd multicluster
for ctx in kind-west kind-east; do
echo "Installing on cluster: ${ctx}"
linkerd --context=${ctx} multicluster install |
kubectl --context=${ctx} apply -f - || break
echo "-------------"
done
# 8. Check Linkerd multicluster
for ctx in kind-west kind-east; do
echo "Checking gateway on cluster: ${ctx}"
kubectl --context=${ctx} -n linkerd-multicluster \
rollout status deploy/linkerd-gateway || break
echo "-------------"
done
# 9. Check load balancer
for ctx in kind-west kind-east; do
echo "Checking load balancer on cluster: ${ctx}"
while [ "$(kubectl --context=${ctx} -n linkerd-multicluster get service \
-o 'custom-columns=:.status.loadBalancer.ingress[0].ip' \
--no-headers)" = "<none>" ]; do
printf '.'
sleep 1
done
echo "-------------"
done
# 10. Link the cluster
linkerd --context=kind-east multicluster link --cluster-name=kind-east |
kubectl --context=kind-west apply -f -I first tried without “step 4 and 5: install Ingress and patch (mesh) Ingress”. However, I failed at checking load balancer at step 9, it stuck there forever with
If I continue next “step 10 Link the cluster“, I will get
I then tired all steps above with “step 4 and 5: install Ingress and patch (mesh) Ingress”, however, I got same the issue. Here are some extra info if it helps:
My first question is that I do need install Ingress, right? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Copy Charles Pretzer comment from Slack here.
Thanks for help! Will do more experiments and report back. |
Beta Was this translation helpful? Give feedback.
-
|
My understanding is that |
Beta Was this translation helpful? Give feedback.
-
|
Oh one sec! Let me try to add these too |
Beta Was this translation helpful? Give feedback.
-
|
Here are my latest files, still got same error.
Here you are. For west cluster: ➜ kubectl get svc -A
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 15m
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 15m
kube-system metrics-server ClusterIP 10.43.148.188 <none> 443/TCP 15m
ingress-nginx ingress-nginx-controller-admission ClusterIP 10.43.247.140 <none> 443/TCP 14m
ingress-nginx ingress-nginx-controller LoadBalancer 10.43.26.8 192.168.32.2 80:30600/TCP,443:31918/TCP 14m
linkerd linkerd-identity ClusterIP 10.43.203.166 <none> 8080/TCP 12m
linkerd linkerd-identity-headless ClusterIP None <none> 8080/TCP 12m
linkerd linkerd-controller-api ClusterIP 10.43.11.109 <none> 8085/TCP 12m
linkerd linkerd-dst ClusterIP 10.43.201.7 <none> 8086/TCP 12m
linkerd linkerd-dst-headless ClusterIP None <none> 8086/TCP 12m
linkerd linkerd-proxy-injector ClusterIP 10.43.101.227 <none> 443/TCP 12m
linkerd linkerd-sp-validator ClusterIP 10.43.219.47 <none> 443/TCP 12m
linkerd-multicluster linkerd-gateway LoadBalancer 10.43.23.242 192.168.32.2 4143:32058/TCP,4181:30590/TCP 8m20s
linkerd-multicluster probe-gateway-k3d-east ClusterIP 10.43.90.7 <none> 4181/TCP 6m39sFor east cluster ➜ kubectl get svc -A
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 17m
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 17m
kube-system metrics-server ClusterIP 10.43.225.93 <none> 443/TCP 17m
ingress-nginx ingress-nginx-controller-admission ClusterIP 10.43.53.241 <none> 443/TCP 16m
ingress-nginx ingress-nginx-controller LoadBalancer 10.43.203.226 192.168.32.4 80:32274/TCP,443:31080/TCP 16m
linkerd linkerd-identity ClusterIP 10.43.171.115 <none> 8080/TCP 14m
linkerd linkerd-identity-headless ClusterIP None <none> 8080/TCP 14m
linkerd linkerd-controller-api ClusterIP 10.43.102.252 <none> 8085/TCP 14m
linkerd linkerd-dst ClusterIP 10.43.77.165 <none> 8086/TCP 14m
linkerd linkerd-dst-headless ClusterIP None <none> 8086/TCP 14m
linkerd linkerd-proxy-injector ClusterIP 10.43.218.1 <none> 443/TCP 14m
linkerd linkerd-sp-validator ClusterIP 10.43.156.178 <none> 443/TCP 14m
linkerd-multicluster linkerd-gateway LoadBalancer 10.43.29.192 192.168.32.4 4143:31653/TCP,4181:31837/TCP 10m |
Beta Was this translation helpful? Give feedback.
-
|
After changing to the port EAST_IP=$(kubectl --context="k3d-east" get service --namespace=ingress-nginx ingress-nginx-controller --output='go-template={{ (index .status.loadBalancer.ingress 0).ip }}')
linkerd --context=k3d-east multicluster link \
--cluster-name=k3d-east \
--api-server-address="https://${EAST_IP}:6443" | \
kubectl --context=k3d-west apply --filename=-Now my error becomes ➜ linkerd --context=k3d-west multicluster check
linkerd-multicluster
--------------------
√ Link CRD exists
√ Link resources are valid
* k3d-east
× remote cluster access credentials are valid
* failed to connect to API for cluster: [k3d-east]: Get "https://192.168.32.4:6443/version?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
see https://linkerd.io/2.10/checks/#l5d-smc-target-clusters-access for hints
W0803 11:15:00.463317 93989 transport.go:260] Unable to cancel request for promhttp.RoundTripperFunc
× clusters share trust anchors
Problematic clusters:
* k3d-east: unable to fetch anchors: Get "https://192.168.32.4:6443/api/v1/namespaces/linkerd/configmaps/linkerd-config?timeout=30s": context deadline exceeded
see https://linkerd.io/2.10/checks/#l5d-multicluster-clusters-share-anchors for hints
√ service mirror controller has required permissions
* k3d-east
√ service mirror controllers are running
* k3d-east
Status check results are × |
Beta Was this translation helpful? Give feedback.
-
|
These two errors: not really affect the actual multi-cluster functions. The communication between clusters work well. My final working solution to multi clusters is posted at |
Beta Was this translation helpful? Give feedback.
Copy Charles Pretzer comment from Slack here.
Thanks for help! Will do more experiments and report back.