Isn't this just a podcast website, or is there something more to it? Why on earth would a podcast website need Kube?
New setup for 2020
11–20 of 58 posts
Re: New setup for 2020
#12I'd be interested in learning more about the move from Concourse to Circle (I'm a notorious Concourse fanboy). What went well, what didn't, what you miss, what prompted it -- that sort of thing.
Re: New setup for 2020
#13Isn't this just a podcast website, or is there something more to it? Why on earth would a podcast website need Kube?
A good portion of the article (the beginning portion no less!) is explicitly meant to answer exactly this question. When the writer anticipates this question and preemptively responds to it, least we could do is discuss their answer rather than repeat the question.
Re: New setup for 2020
#14woo self-managed postgres on k8s
vendor-managed DBs limit plugins + versions, excited to see this space advance
Re: New setup for 2020
#15Isn't changelog.com mostly a static site? What kind of workloads do they run/monitor/update with all this infrastructure?
I think they're sponsored by linode, and they're developer-themed -- there may be team / content reasons to use a lot of unnecessary tools in order to review them
Re: New setup for 2020
#16>>> We no longer provision load balancers, or configure DNS; we simply describe the resources that we need, and Kubernetes makes it happen.
This is (part) of what keeps me in the stone age. You are provisioning load balancers and DNS - but just one step removed through k8s
And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug.
And so it feels a bit like "magic abstraction". And then to peek through the abstraction you suddenly not only need to know about DNS and which machine is running bind, but also how kubernetes internally stores it's DNS config and how it spits that out and what version they changed it with.
In other words you have to become expect in two things to debug it.
And maybe it's worth it - but I struggle to see why it's not simpler to keep my install scripts going.
(OK I guess I am writing my own answer - but surely the point is what is the simplest level of thin install scripts needed to deploy containers?)
Re: New setup for 2020
#17>>> We no longer provision load balancers, or configure DNS; we simply describe the resources that we need, and Kubernetes makes it happen. This is (part) of what keeps me in the stone age. You are provisioning load balancers and DNS - but just one step removed through k8s And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug. And so it feels a bit…
i think the idea is that k8s does away with having to glue all those pieces of infra together, not that you lose understanding of how it all works together. part of the headache with managing infra is that it rots over time... things come and go (sysv to systemd, apt/snap/whatever, config files change, things break). it's easier to keep up to date on k8s than all the disparate parts of the OS and provider-specific APIs and whatnot
Re: New setup for 2020
#18Isn't this just a podcast website, or is there something more to it? Why on earth would a podcast website need Kube?
Yea that is what I was thinking. And the next thing was what is the price difference. A bit of me thinks this is just some people doing some really cool tech work for the sake of it, which I can't fault them for.
Re: New setup for 2020
#19The static files should definitely be on some kind of object storage like S3, that's what it's built for. Much faster, more reliable, more scalable, and likely much cheaper too.
As for persistent volumes, might be better to just offload Postgres to a managed DB service and downsize the K8S instances, or use something like CockroachDB which is natively distributed and can make use of local volumes instead.
Re: New setup for 2020
#20Isn't changelog.com mostly a static site? What kind of workloads do they run/monitor/update with all this infrastructure?
I think they're sponsored by linode, and they're developer-themed -- there may be team / content reasons to use a lot of unnecessary tools in order to review them
This quote from Adam on our episode about the setup explains some of our motivations here:
> It’s worth noting that we don’t really need what we have around Kubernetes. This is for fun, to some degree. One, we love Linode, they’re a great partner… Two, we love you, Gerhard, and all the work you’ve done here… We don’t really need this setup. One, it’s about learning ourselves, but then also sharing that. Obviously, Changelog.com is open source, so if you’re curious how this is implemented, you can look in our codebase. But beyond that, I think it’s important to remind our audience that we don’t really need this; it’s fun to have, and actually a worthwhile investment for us, because this does cost us money (Gerhard does not work for free), and it’s part of this desire to learn for ourselves, and then also to share it with everyone else… So that’s fun. It’s fun to do.