profile
viewpoint

Ask questionsDev spaces with Linkerd - Pods stuck on initalizing

Hey Guys,

I'm having some trouble using dev spaces with a linkerd enabled kubernetes cluster. Linkerd is set to auto-inject into any deployments created in a particular namespace. But it seems that when using azds up the deploy hangs and pods get stuck initalizing.

I've deploy other containers to the namespace successfully. Any ideas?

Heres the deployment:

Name:                   webapplication1
Namespace:              darren
CreationTimestamp:      Fri, 05 Apr 2019 13:36:54 +0100
Labels:                 app=webapplication1
                        chart=webapplication1-0.1.0
                        draft=draft-app
                        heritage=Tiller
                        linkerd.io/control-plane-ns=linkerd
                        linkerd.io/proxy-deployment=webapplication1
                        release=azds-842081-darren-webapplication1
Annotations:            deployment.kubernetes.io/revision=1
Selector:               app=webapplication1,release=azds-842081-darren-webapplication1
Replicas:               1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:       app=webapplication1
                draft=draft-app
                linkerd.io/control-plane-ns=linkerd
                linkerd.io/proxy-deployment=webapplication1
                release=azds-842081-darren-webapplication1
  Annotations:  buildID=
                linkerd.io/created-by=linkerd/proxy-injector stable-2.2.1
                linkerd.io/proxy-version=stable-2.2.1
  Init Containers:
   linkerd-init:
    Image:      gcr.io/linkerd-io/proxy-init:stable-2.2.1
    Port:       <none>
    Host Port:  <none>
    Args:
      --incoming-proxy-port
      4143
      --outgoing-proxy-port
      4140
      --proxy-uid
      2102
      --inbound-ports-to-ignore
      4190,4191
    Environment:  <none>
    Mounts:       <none>
  Containers:
   webapplication1:
    Image:        webapplication1:devspaces-x0169ed8076cfdb63
    Port:         80/TCP
    Host Port:    0/TCP
    Environment:  <none>
    Mounts:       <none>
   linkerd-proxy:
    Image:       gcr.io/linkerd-io/proxy:stable-2.2.1
    Ports:       4143/TCP, 4191/TCP
    Host Ports:  0/TCP, 0/TCP
    Liveness:    http-get http://:4191/metrics delay=10s timeout=1s period=10s #success=1 #failure=3
    Readiness:   http-get http://:4191/metrics delay=10s timeout=1s period=10s #success=1 #failure=3
    Environment:
      LINKERD2_PROXY_LOG:                           warn,linkerd2_proxy=info
      LINKERD2_PROXY_CONTROL_URL:                   tcp://linkerd-proxy-api.linkerd.svc.cluster.local:8086
      LINKERD2_PROXY_CONTROL_LISTENER:              tcp://0.0.0.0:4190
      LINKERD2_PROXY_METRICS_LISTENER:              tcp://0.0.0.0:4191
      LINKERD2_PROXY_OUTBOUND_LISTENER:             tcp://127.0.0.1:4140
      LINKERD2_PROXY_INBOUND_LISTENER:              tcp://0.0.0.0:4143
      LINKERD2_PROXY_DESTINATION_PROFILE_SUFFIXES:  .
      LINKERD2_PROXY_POD_NAMESPACE:                  (v1:metadata.namespace)
      LINKERD2_PROXY_INBOUND_ACCEPT_KEEPALIVE:      10000ms
      LINKERD2_PROXY_OUTBOUND_CONNECT_KEEPALIVE:    10000ms
      LINKERD2_PROXY_ID:                            webapplication1.deployment.darren.linkerd-managed.linkerd.svc.cluster.local
    Mounts:                                         <none>
  Volumes:                                          <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      False   MinimumReplicasUnavailable
  Progressing    True    ReplicaSetUpdated
OldReplicaSets:  <none>
NewReplicaSet:   webapplication1-674db99f7c (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  3m    deployment-controller  Scaled up replica set webapplication1-674db99f7c to 1
Azure/dev-spaces

Answer questions grampelberg

Totally possible!

useful!

Related questions

Bad Gateway returned when not in debug mode hot 1
Helm install failed hot 1
Invalid dockerfile generated hot 1
Add support for multiple project azds debug configuration on vscode extension hot 1
Github User Rank List