| • The host is filling in for Chris Fisher who may have COVID-19
|
| • Techno Tim joins the episode as a guest and has recently reached 100,000 subscribers on YouTube
|
| • Tim launched "100 Days of HomeLab" initiative where participants will complete a task related to home automation and self-hosting every day for 100 days
|
| • 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 |
