Welcome to the Linux Foundation Forum!

Lab 11.1. Service Mesh

Hi, could you help me on this issue?

[email protected]:~$ linkerd viz install | kubectl apply -f -
Waiting for control plane to become available
Waiting for control plane to become available
Waiting for control plane to become available

I don't know what can be wrong

thanks,
Arturo

Comments

  • chrispokorni
    chrispokorni Posts: 1,549

    Hi @eporart,

    Please try to re-install linkerd. If a re-installation does not help, please provide the outputs of the following two commands:

    kubectl get nodes -o wide

    kubectl get pods -A

    Regards,
    -Chris

  • bdkdavid
    bdkdavid Posts: 32

    run linkerd check
    make sure everything is green

    output

    Linkerd core checks

    kubernetes-api

    √ can initialize the client
    √ can query the Kubernetes API

    kubernetes-version

    √ is running the minimum Kubernetes API version
    √ is running the minimum kubectl version

    linkerd-existence

    √ 'linkerd-config' config map exists
    √ heartbeat ServiceAccount exist
    √ control plane replica sets are ready
    √ no unschedulable pods
    √ control plane pods are ready
    √ cluster networks can be verified
    √ cluster networks contains all node podCIDRs

    linkerd-config

    √ control plane Namespace exists
    √ control plane ClusterRoles exist
    √ control plane ClusterRoleBindings exist
    √ control plane ServiceAccounts exist
    √ control plane CustomResourceDefinitions exist
    √ control plane MutatingWebhookConfigurations exist
    √ control plane ValidatingWebhookConfigurations exist
    √ proxy-init container runs as root user if docker container runtime is used

    linkerd-identity

    √ certificate config is valid
    √ trust anchors are using supported crypto algorithm
    √ trust anchors are within their validity period
    √ trust anchors are valid for at least 60 days
    √ issuer cert is using supported crypto algorithm
    √ issuer cert is within its validity period
    √ issuer cert is valid for at least 60 days
    √ issuer cert is issued by the trust anchor

    linkerd-webhooks-and-apisvc-tls

    √ proxy-injector webhook has valid cert
    √ proxy-injector cert is valid for at least 60 days
    √ sp-validator webhook has valid cert
    √ sp-validator cert is valid for at least 60 days
    √ policy-validator webhook has valid cert
    √ policy-validator cert is valid for at least 60 days

    linkerd-version

    √ can determine the latest version
    √ cli is up-to-date

    control-plane-version

    √ can retrieve the control plane version
    √ control plane is up-to-date
    √ control plane and cli versions match

    linkerd-control-plane-proxy

    √ control plane proxies are healthy
    √ control plane proxies are up-to-date
    √ control plane proxies and cli versions match

    Status check results are √

  • eporart
    eporart Posts: 20

    thanks for your comments
    linkerd was uninstall and install again... this works for me

    linkerd uninstall | kubectl delete -f -
    clusterrole.rbac.authorization.k8s.io "linkerd-heartbeat" deleted
    clusterrole.rbac.authorization.k8s.io "linkerd-linkerd-controller" deleted
    clusterrole.rbac.authorization.k8s.io "linkerd-linkerd-destination" deleted
    clusterrole.rbac.authorization.k8s.io "linkerd-linkerd-identity" deleted
    clusterrole.rbac.authorization.k8s.io "linkerd-linkerd-proxy-injector" deleted
    clusterrole.rbac.authorization.k8s.io "linkerd-linkerd-sp-validator" deleted

    [email protected]:~$ kubectl get pod -A | grep linkerd

    linkerd linkerd-destination-654f666554-rb9rn 4/4 Running 0 5m10s
    linkerd linkerd-identity-569cfff464-48njb 2/2 Running 0 5m10s
    linkerd linkerd-proxy-injector-55c9b5f46f-4khqt 2/2 Running 0 5m9s

    thanks,
    eporart

Categories

Upcoming Training