From 4fd74aa5a9a6158ed6b6fca53d63afa85b52e35f Mon Sep 17 00:00:00 2001 From: Daniel Cosme Date: Fri, 17 Apr 2026 15:23:56 -0400 Subject: [PATCH] First commt --- README.md | 30 ++++++++++++++++++++++++++++++ install_k3s.sh | 5 +++++ 2 files changed, 35 insertions(+) create mode 100644 README.md create mode 100755 install_k3s.sh diff --git a/README.md b/README.md new file mode 100644 index 0000000..8b42881 --- /dev/null +++ b/README.md @@ -0,0 +1,30 @@ +# GitOps +> A set of "best practices" where the entire code delivery process is controlled via Git, +including infrastructure and application definition as code and automation to complete updates +and rollbacks. + +The key GitOps Principles +- The entire system (infrastructure and applications) is described declaratively. +- The canonical desired system state is versioned in Git. +- Changes approved are automated and applied to the system. +- Software agents ensure correctness and alert on divergence. + +https://opengitops.dev/ + +Key points for a Kubernetes cluster: +1. The state of the cluster is always described in Git. Git holds everything for the application +and not just the source code. +2. There is no external deployment system with full access to the cluster. The cluster itself +is pulling changes and deployment information. +3. The GitOps controller is running in a constant loop and always matches the Git state with the +cluster state (reconciliation loop). + +## flux vs ArgoCD +Flux is more CLI Driven +ArgoCD has a richer GUI + +## Flux +Prerequisites: +- Kubernetes Cluster +- Github (giea, etc) personal access token + diff --git a/install_k3s.sh b/install_k3s.sh new file mode 100755 index 0000000..f36629d --- /dev/null +++ b/install_k3s.sh @@ -0,0 +1,5 @@ +#!/bin/sh + +sudo mkdir -p /etc/rancher/k3s +curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable=helm-controller" sh +sudo systemctl status k3s.service