Skip to content

Noticing weird kubernetes pods being deployed and terminated immediately  #1089

Closed

Description

When I use the annotation "sidecar.jaegertracing.io/inject": "true" , there are extra pods that get created that terminate right away. IN my example below, the two api pods that get created named api-5955f589d5-fkpfg and api-5955f589d5-rhhm6 are created and immediately terminated. the correct replicaset that ends up being persisted and deployed are the first 3 api pods (with ages 1s and 2s). Anybody run into this before?

NAME                              READY   STATUS              RESTARTS   AGE
api-57ffc5c59b-bq2vb              0/2     ContainerCreating   0          1s
api-57ffc5c59b-hvr9l              0/2     ContainerCreating   0          1s
api-57ffc5c59b-jv5zx              0/2     ContainerCreating   0          2s
api-5955f589d5-8fjml              2/2     Running             0          74m 
api-5955f589d5-fkpfg              1/2     Terminating         0          9s
api-5955f589d5-rhhm6              1/2     Running             0          9s
client-78d7747758-b8m2b           1/1     Running             0          74m
client-78d7747758-wrmrp           0/1     Terminating         0          9s
client-7c74cd6d89-ptn2z           0/1     ContainerCreating   0          1s
client-7c74cd6d89-q2lxg           0/1     ContainerCreating   0          2s```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    needs-infoWe need some info from you! If not provided after a few weeks, we'll close this issue.questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions