ArgoCD
Use case: To be able to deploy and manage PostgreSQL clusters with GitOps and to provide an auditable and easily understandable system for developers to manage their own Postgres clusters from the same git repo. Brief description of the tech involved: GitOps with ArgoCD: GitOps is a software and deployment
Kubernetes
In this final post of the Going Mobile series, I'll go over some issues I have faced while deploying the system, and provide a summary of the solutions I chose to resolve them. Networking (again): svclb timing out: Upon deploying the nodes in different locations I realised that
Kubernetes
3 Parts: This post will be split into 3 parts: * Networking * Monitoring * Chaos Engineering Networking: The networking stack is comprised of 3 main parts: * MagicDNS with Headscale * HAProxy * Traefik MagicDNS with Headscale The Headscale server handles the DNS resolution with MagicDNS, an example of how this is implemented in the
Kubernetes
A change of plans: The original design in part 2 had a few missing parts: * It didn't include the hosting of the Headscale server required for our Tailscale overlay network. * The assumption of being able to have 2 physical location wasn't correct in the context of
Kubernetes
The Plan: The part that matters Part 1: Identifying System Requirements Based on the outlines from Part 1, the requirements for our system are as follows: 1. Highly available, geographically distributed system 2. Distributed replicated storage 3. Ability to run argoCD, code-server, hakatime, and Nextcloud together, at a minimum Part
Kubernetes
Introduction "Going Mobile" is a blog series that documents my journey to create a fully distributed system for both personal and professional use, which will allow me to work remotely from anywhere in the world with an internet connection. The project is primarily focused on creating a distributed