archived the channel

@Jonathan Tobe has joined the channel

Adding @U010XGY9B46 bot

oooooohhhh…Thanks @Erik Osterman (Cloud Posse)

Just got mine as well! Thanks for the heads up @Erik Osterman (Cloud Posse)!

see u there @Erik Osterman (Cloud Posse)!

Just got my ticket

@UUB28NLDS help keep tabs! 😉

Pretty good news I'd say.

@mrwacky not too shabby

(part of SCALE conference i think)

See ya'll at DevOps Days!

Won’t be able to make it, but hope everyone else can!!

@channel Is your lack of versioning leading to system instability? Learn about the importance of versioning at WLAD #5 (Jan 30th @ 6pm), right here at GumGum HQ in Santa Monica: https://www.meetup.com/West-LA-DevOps/events/267897847/

SCALE early bird registration ends this weekend www.socallinuxexpo.org
if you want your low cost pass for even cheaper, nows the time to buy

Happy NY! 😃

Happy New Year Los Angeles! 🎉

#represent!

👍️ great response erik

option (1) is 80% more work with 20% more benefit

80/20 rule

2) from an HA perspective, the registry mirror is sufficient.

1) from a security perspective, you should explicitly replicate or produce an image in your own repo for every package you depend on. for smaller team, this might be a lot of overhead. it will shield you also from upstream outages.

I'd argue:

or you can just use a mirror that that has a pull-through cache (as you describe) and address the immediate risk of being crippled by upstream outages.

sure you can take on the burden of pushing those to your own repos - that's great (but a lot of work)

in our case: prometheus, grafana, keycloak, gatekeeper, kubecost, and 2 dozen other third-party vendors

chances are you don't rely on just your software

you could do them in parallel in ci step (push to codefreshf registry + push to ECR)

@Erik Osterman (Cloud Posse) is there a big difference in registry mirroring vs just pushing to 2 different registries?

I just don’t know where the line is drawn between open source and enterprise. Artifactory is cool and all, but I know their pricing is insane.

Maybe go all the way and use something like Artifactory to be the pull-through cache for everything, not just docker images. https://jfrog.com/artifactory/features/

@Jeremy G (Cloud Posse) we should add this to next rollout

@Corey Gale has joined the channel

Not sure what happens if the mirror is offline - I presume it attempts upstream

So it seems like it’s easy enough to deploy a pass thru registry in cluster and then configure the mirror to use it

Looks like this is natively supported by Kops

Pia?

But in researching this some more, I learned about the registry mirror option built into Docker

I think mirroring the images to ECR is a PIA