text stringlengths 7 369 |
|---|
• The host mentions upcoming UK meetup in August with a tentative date of August 5th and encourages listeners to suggest venues in London |
• Discussion of DevOps and the need for generalists who know a little about everything |
• Mention of home labbing and the launch of a YouTube series "100 days of home lab" |
• Creation of a hashtag #100daysofhome lab to get people motivated and share their experiences |
• Comparison between daily standup updates in software development and the updates being shared on the hashtag |
• Discussion of the long-term plan for the initiative, which is not clearly defined but focused on creating a community and helping people with infrastructure challenges |
• The speaker's experience with their YouTube video on Kubernetes and the unexpected response from viewers |
• Defining what a "home lab" means, as it can have different interpretations for various people |
• The concept of home labs as a place to experiment and test new technologies in a safe environment |
• Common issues that arise when working in home labs, such as accidental destruction of production environments or equipment failures |
• The speaker's own experiences with making mistakes while working on production systems, including deleting a load balancer and causing alerts to fire |
• The importance of self-hosting and experimentation for developers, even if it means taking on additional responsibilities at home |
• Setting up a home lab for experimenting and testing without affecting production services |
• Using existing equipment or upgrading current PC to create a home lab |
• Importance of memory in a home lab setup |
• Various options for creating a home lab, from Raspberry Pis to enterprise-grade servers |
• Showcased storage capacities of guests on the wiki.selfhosted.show leaderboard |
• The speaker praises Linode's customer support and services |
• The speaker uses Linode's cloud dashboard and S3 object storage to run Nextcloud for their network |
• The speaker discusses the benefits of using Linode over other major cloud providers due to its pricing (30-50% cheaper) |
• The speaker expresses interest in learning about Kubernetes and K3S, a lightweight way to run containers on the edge |
• The speaker shares personal experiences with setting up and managing Kubernetes clusters and notes the complexity involved |
• Challenges of setting up a highly available Kubernetes setup |
• Lowest barrier of entry for a home lab scenario |
• Comparison of using etcd vs MySQL as the backend database |
• Complexity of replication and load balancing |
• Industry standard practices vs custom setups |
• Importance of choosing storage solutions before running services |
• Stateful applications in Kubernetes require management of persistent state and storage |
• NFS and other solutions can be used for storage, but introduce single points of failure |
• Highly available services should not rely on a single point of failure for storage or databases |
• Stateless applications can scale more easily in Kubernetes |
• Kubernetes can automatically recover from node failures by recreating pods on other nodes |
• 12 factor app architecture is recommended for dev shops to manage complexity and ensure scalability |
• Overview of Helm charts and their use in running applications on Kubernetes clusters |
• Discussion of the challenges and "gotchas" of managing user permissions and other configurations in Kubernetes |
• Introduction to GitOps and its principles for declaratively defining cluster state through Git |
• Explanation of how GitOps works, including the use of manifests and pull requests to influence cluster state |
• Benefits of using GitOps, including reproducibility and accountability of changes |
• Comparison of GitOps with other DevOps practices, such as Ansible |
• GitOps approach to Kubernetes management |
• Declarative vs imperative configuration |
• Benefits of GitOps: simplicity, ease of rebuilding, and version control |
• Drawbacks of GitOps: additional process steps for minor changes |
• Argo CD as a tool for implementing GitOps |
• Talescale.com: a zero-config VPN with firewall rules and subnet router technology |
• Pine Note developer edition review and discussion |
• E-ink display technology and costs |
• Linus (security tool) and other security scanning tools |
• Cybersecurity best practices for systems and networks |
• Tailscale and port management in firewalls |
• Alternatives to Raspberry Pi, including Orange Pi boards |
• The host mentions their YouTube channel "Techno Tim" and provides ways to access it |
• The host thanks Site Reliability Engineers (SRE) for making the show possible |
• The host promotes supporting the Jupiter Broadcasting Network and its website Jupiter.party |
• Upcoming events are mentioned, including a London Meetup on August 5th |
• Contact information is provided for reaching out to the host or the show |
[0.00 --> 6.44] Well, welcome to episode 73, everybody. My usual co-host, Chris Fisher, is unfortunately out sick |
[6.44 --> 11.92] this week. We think he might have the rona. So please send him your best wishes. But joining me, |
[11.98 --> 16.32] I have a very special guest. I have Techno Tim. Hi, Tim. Hey, thanks for having me. |
[16.58 --> 20.02] Well, thank you. Absolutely. Last minute, I messaged Tim yesterday and said, |
[20.84 --> 24.92] yeah, Chris isn't feeling so good. Do you happen to be free tomorrow night? And |
[24.92 --> 31.06] serendipitously, he was. So here we are. So this episode, we're going to be talking about all |
[31.06 --> 37.24] things Homelab. Tim just passed 100,000 subscribers on YouTube. Congratulations. |
[38.08 --> 39.70] Thank you. Thank you. Yeah, it's crazy. |
[40.02 --> 44.92] And as part of that, I think you launched a 100 days of Homelab initiative, which we'll come to |
[44.92 --> 50.00] in just a minute. But before we get there, usual plugs for things like the Discord at selfhosted.show |
[50.00 --> 54.90] slash Discord. We've got over 4,000 people over there talking about all things self-hosted. |
[54.92 --> 61.40] Hosted, maker spaces, home assistant, all that kind of stuff. You all know as well that we've |
[61.40 --> 68.04] got a UK meetup coming up in August. The date did change due to some flight stuff with me. So |
[68.04 --> 74.22] the new date is provisionally August the 5th. We're still trying to find a venue. And now if you have |
[74.22 --> 78.40] any ideas about where we might host this thing in London, I've been ringing around a few places the |
[78.40 --> 82.92] last few days trying to find a pub with a big beer garden or something like that so that we don't have |
[82.92 --> 89.04] to hang out on like a village green or something, you know, the requirements are outdoors, has toilets, |
[89.28 --> 94.70] has beer. I think that's probably a pretty good recipe for a good meetup. So if you have any ideas |
[94.70 --> 100.74] about where we might do this in London general area, let me know. I'm on Twitter at ironicbadger. |
[100.74 --> 108.36] So remember, that's the provisional date is August the 5th. And I think that's about it. So it's |
[108.36 --> 113.00] probably about time we start talking about the 100 days of HomeLab. What madman came up with a |
[113.00 --> 115.08] 100 day hour a day challenge? |
[115.90 --> 121.78] Yeah, me, I guess. You know, 100 days of HomeLab is something that I've been noodling on for, |
[121.94 --> 127.52] I'd say, about six months. You know, I'm a software developer and software developers have had a |
[127.52 --> 132.74] challenge for a while. It's the 100 days of code. And it pops up in my feed everywhere. And I think, |
[132.82 --> 140.56] what a great initiative. You know, you form a habit by doing something once a day for an hour a day |
[140.56 --> 145.56] with a goal in mind and march towards that goal for 100 days. And by the end of the 100 days, |
[145.68 --> 150.76] you'll learn something. Maybe you'll learn how to program. Maybe you build a website, whatever it is. |
[151.24 --> 154.74] Maybe you'll learn that actually you don't like the thing that you signed up to do quite as much as |
[154.74 --> 159.14] you thought you did. That is true, too. Yeah, very good point. Yeah, you might discover this is not |
[159.14 --> 163.78] for me. Like I thought programming wasn't for me in college, but now it's programming for me out of |
[163.78 --> 169.34] college. You know, I had that idea of, OK, how can I get people in the HomeLab community, one, |
[169.44 --> 175.10] together and motivated and excited about doing stuff? I'm excited. I know a lot of people are, |
[175.20 --> 180.94] but, you know, just kind of bringing people together. And the whole entire landscape of a HomeLab, |
[180.94 --> 185.80] if you think about it, it's gigantic. But, you know, I kind of think of it as networking, |
[186.28 --> 192.00] storage, infrastructure, automation, a little bit of DevOps, some hosting. You know, it's a lot of |
[192.00 --> 197.40] different things to a lot of different people. And, you know, that landscape is rapidly changing, |
[197.64 --> 201.40] you know, especially in the last couple of years, if you think of infrastructure as code or |
[201.40 --> 206.82] anything or storage, storage now in Kubernetes, storage everywhere. It's all changing, |
[206.82 --> 212.82] you know, software defined networks. And so I thought, hmm, I have 100K coming up and what can |
[212.82 --> 217.24] I do that has, you know, has as related to 100? And that's what I thought. I thought, well, |
[217.34 --> 222.28] maybe I'll launch something around then. I was six months out and I thought, you know what, |
[222.36 --> 228.26] I'm just going to do what I do best and procrastinate for six months until this, you know, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.