image-registry is tied to Sirupsen (uppercase) about image-registry HOT 6 CLOSED

@deads2k fyi when you wonder why image-registry is still using kube 1.9 deps.

from image-registry.

@deads2k fyi when you wonder why image-registry is still using kube 1.9 deps.

@derekwaynecarr time bombs. Luckily we got this split out just in time.

from image-registry.

for what it's worth, cherry-picking+carrying the commit actually doesn't look too bad:
distribution/distribution@a97d7c0

the main problem is they did that after moving to dep, so we'd have to manage the godeps changes.

from image-registry.

After rebase, we no longer use the github.com/Sirupsen/logrus.

$ git grep -c Sirupsen 
glide.lock:1
glide.yaml:1
vendor/github.com/bshuster-repo/logrus-logstash-hook/CHANGELOG.md:1
vendor/github.com/bshuster-repo/logrus-logstash-hook/logstash_formatter.go:1
vendor/github.com/google/cadvisor/Godeps/Godeps.json:1

$ git grep sirupsen |wc -l
330

from image-registry.

@legionus looks like it's still in our glide.yaml, can you submit a PR removing it that closes this issue?

from image-registry.

and bump us to kube 1.11 deps while you're at it.

from image-registry.