deployment not creating pod at all

[che...@gmail.com]

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.

[Ahmet Alp Balkan]

Can you look at "kubectl get events -w" and see what is happening when you create the deployment? I wonder if there's any issue with replicaset that is not shown in the events for deployment.

--
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+unsubscribe@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.

[che...@gmail.com]

No events at all.
I just figured out it is because I defined multiple labels. If I just use one label, everything is fine. Is this a bug?

Labels: app=naas
component=symphony

Use one label will work.

regards
-weiwen

On Monday, May 15, 2017 at 1:44:17 PM UTC-6, Ahmet Alp Balkan wrote:
> Can you look at "kubectl get events -w" and see what is happening when you create the deployment? I wonder if there's any issue with replicaset that is not shown in the events for deployment.
>
>
> On Mon, May 15, 2017 at 12:36 PM, <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.
>
>
>
> --
>
> 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-use...@googlegroups.com.
>
> To post to this group, send email to kubernet...@googlegroups.com.

[Ahmet Alp Balkan]

It might be helpful to paste your deployment manifest yaml file here.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.

[che...@gmail.com]

Here it is with both labels:
thanks

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
labels:
component: symphony
app: naas
name: symphony
namespace: symphony
spec:
replicas: 1
template:
metadata:
labels:
component: symphony
app: naas
spec:
containers:
- image: registry.naas.aws.charterlab.com:4567/symphony/api:17.05.10
name: api
command: ["sleep"]
args: ["300000"]
ports:
- containerPort: 8000
resources:
requests:
memory: 256Mi
limits:
memory: 1024Mi

[Ahmet Alp Balkan]

Interesting, I've been able to change the image to busybox from your manifest and deploy it as is, and the pod came up.

[che...@gmail.com]

> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-use...@googlegroups.com.
>
> To post to this group, send email to kubernet...@googlegroups.com.

>
> Visit this group at https://groups.google.com/group/kubernetes-users.
>
> For more options, visit https://groups.google.com/d/optout.

I should mention the version I am on now:

Kubernetes: 1.5.2

Will keep an eye on it later
thanks

[vidhyash...@gmail.com]

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.

[David Rosenstrauch]

It looks like the pods died for some reason. Try a "kubectl describe
pod" and/or a "kubectl logs" on one of the 2 dead pods to see what happened.

HTH,

DR

[vidhyash...@gmail.com]

@david Thanks for the reply. I figured out the issue by checking kubectl describe replicaset. We were using Istio automatic sidecar injection. The istio-sidecar-injector pod was stalled in containercreating state. but the webhook was created. Hence pods of any other service were not getting created. Removing the automatic sidecar injector deployment fixed the issue for me.