# Traefik DaemonSet Died with wrong image

**URL:** <https://community.traefik.io/t/traefik-daemonset-died-with-wrong-image/1391>\
**Category:** Traefik v1\
**Tags:** kubernetes-ingress\
**Created:** [August 30, 2019, 5:50pm UTC](https://community.traefik.io/t/traefik-daemonset-died-with-wrong-image/1391 "2019-08-30T17:50:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![skuppa](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/skuppa/32/5702_2.png) [@skuppa](https://community.traefik.io/u/skuppa)\
**Post date:** [August 30, 2019, 5:50pm UTC](https://community.traefik.io/t/traefik-daemonset-died-with-wrong-image/1391/1 "2019-08-30T17:50:35Z")

</div>

We have traefik configured in our kubernetes clusters, about 20 nodes. The traffic increased to 2K requests/minute then our traefik daemon died, here is sequence of log observed.

1. kubectl received SyncLoop: DELETE for traefik and killed the running traefik container
2. kubectl trying to start the same container but container not found and it gave up after 5 retries.
3. kubectl trying to pull traefik image `1.17.4` (future version #) which is not exists in docker hub. After few retry, it gave up.
4. At this time.. all traefik pod (daemonset) died and noticed a new daemonset configuration was created and old one was deleted without anyone touching the system.
5. After 15 mins, we added a new node and it started. Also, all existing nodes received SyncLoop: ADD for traefik then new version of traefik image, `1.7.14` was downloaded and traefik started in all nodes.

The question here is, why traefik is trying to download `1.17.4` not-released version from docker repo? Why daemonset got deleted and created again?

Thanks in Adv,  
-Sridharan