On Tuesday, 16 May 2017 01:06:20 UTC+5:30, che...@gmail.com  wrote:
> Dear Expert,
> 
> I defined a deployment which got created by not bring up any pod at all with 
> following details. Any help is appreciated:
> 
> # kubectl describe deployment symphony
> Name:                 symphony
> Namespace:            symphony
> CreationTimestamp:    Mon, 15 May 2017 19:25:34 +0000
> Labels:                       app=naas
>                       component=symphony
> Selector:             app=naas,component=symphony
> Replicas:             0 updated | 1 total | 0 available | 0 unavailable
> StrategyType:         RollingUpdate
> MinReadySeconds:      0
> RollingUpdateStrategy:        1 max unavailable, 1 max surge
> OldReplicaSets:               <none>
> NewReplicaSet:                <none>
> No events.

I am facing exactly the same issue. Deployment gets created but not pod is 
started. When I check the replicaset it shows 
NAME                                         DESIRED   CURRENT   READY     AGE
test-pod-v1-66775f865b                   2         0         0         38s


The same yml was working fine for me. I suddenly got into this issue. 

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
  • [kubernetes-... chenww
    • Re: [ku... 'Ahmet Alp Balkan' via Kubernetes user discussion and Q&A
      • Re:... chenww
        • ... 'Ahmet Alp Balkan' via Kubernetes user discussion and Q&A
    • [kubern... chenww
      • Re:... 'Ahmet Alp Balkan' via Kubernetes user discussion and Q&A
    • [kubern... vidhyashankar . it
      • Re:... David Rosenstrauch
        • ... vidhyashankar . it

Reply via email to