Welcome to the Linux Foundation Forum!

Lab 7.2. Service Mesh and Ingress Controller - missing step

Posts: 2
edited August 2022 in LFD259 Class Forum

hi All,

Installation steps in point 1 seems to miss one command.

  • When I follow the instruction precheck works fine:

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

pre-kubernetes-setup
√ control plane namespace does not already exist
√ can create non-namespaced resources
√ can create ServiceAccounts
√ can create Services
√ can create Deployments
√ can create CronJobs
√ can create ConfigMaps
√ can create Secrets
√ can read Secrets
√ can read extension-apiserver-authentication configmap
√ no clock skew detected

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

Status check results are √

  • However then
    $ linkerd install | kubectl apply -f -

Linkerd CRDs must be installed first. Run linkerd install with the --crds flag.
error: no objects passed to apply

  • It seems like one step in instruction is missing:

$ linkerd install --crds | kubectl apply -f -

Rendering Linkerd CRDs...
Next, run linkerd install | kubectl apply -f - to install the control plane.
customresourcedefinition.apiextensions.k8s.io/authorizationpolicies.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/httproutes.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/meshtlsauthentications.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/networkauthentications.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/serverauthorizations.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/servers.policy.linkerd.io created
customresourcedefinition.apiextensions.k8s.io/serviceprofiles.linkerd.io created

  • Then "linkerd install | kubectl apply -f -" works fine.

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 2,443

    Hi @rusakl,

    What version of Linkerd is installed on your cluster?

    Regards,
    -Chris

  • Hello!
    I had the same error.
    I'm using the latest stable release of linked

    1. $ linkerd version
    2. Client version: stable-2.12.2
    3. Server version: unavailable

    THIS did work for me!

    1. linkerd install --crds | kubectl apply -f -
    2. # ... a bit of output...
    3. linkerd install | kubectl apply -f -
  • Posts: 2,443

    Hi @mretfaster,

    The crds installation step is not needed for the earlier stable releases of Linkerd, such as 2.11.4, recommended by the lab guide.

    Regards,
    -Chris

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training