k0s VS Flux

I am myself studying it and going through the official documentation and toying with k8s flavors like kind, k3s and k0s.

There's a whole community of hobbyists building Raspberry Pi clusters, porting things to work on various Arm processors, exploring and contributing to minimalist distros like k0s and microk8s, etc.

root@localhost:~# curl -sSLf https://get.k0s.sh | sudo sh Downloading k0s from URL: https://github.com/k0sproject/k0s/releases/download/v1.25.4+k0s.0/k0s-v1.25.4+k0s.0-amd64 k0s is now executable in /usr/local/bin root@localhost:~# k0s install controller --single root@localhost:~# k0s start root@localhost:~# k0s status Version: v1.25.4+k0s.0 Process ID: 1064 Role: controller Workloads: true SingleNode: true Kube-api probing successful: true Kube-api probing last error: root@localhost:~# k0s kubectl cluster-info Kubernetes control plane is running at https://localhost:6443 CoreDNS is running at https://localhost:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. 443/TCP 97s root@localhost:~# k0s kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME localhost Ready control-plane 100s v1.25.4+k0s 172.105.131.23 Ubuntu 22.04.1 LTS 5.15.0-47-generic containerd://1.6.9 root@localhost:~# curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.25.4/bin/linux/amd64/kubectl && chmod +x kubectl && mv kubectl /usr/bin/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 42.9M 100 42.9M 0 0 75.2M 0 --:--:-- --:--:-- --:--:-- 75.3M root@localhost:~# k0s kubeconfig admin > ~/.kube/config root@localhost:~# type kubectl kubectl is hashed (/usr/bin/kubectl) root@localhost:~# kubectl get po,svc -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/kube-proxy-clxh7 1/1 Running 0 3m56s kube-system pod/kube-router-88x25 1/1 Running 0 3m56s kube-system pod/coredns-5d5b5b96f9-4xzsl 1/1 Running 0 4m3s kube-system pod/metrics-server-69d9d66ff8-fxrt7 1/1 Running 0 4m2s NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default service/kubernetes ClusterIP 10.96.0.1 443/TCP 4m20s kube-system service/kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP,9153/TCP 4m8s kube-system service/metrics-server ClusterIP 10.98.18.100 443/TCP 4m2s

I use k0s btw ,and it is fantastic.

Here is link number 1 - Previous text "k0s"

So for example, in my own personal infra repos and for projects I do, Make orchestrates Pulumi, dnscontrol (Holy shit is that tool underrated), ansible, k0s/k0sctl (I run that distro), and all the kubernetes stuff.

I wasn’t able to run Kubernetes in NAS last time I tried it. https://github.com/k0sproject/k0s/issues/1184. As for public access you don’t want to do it for security reasons and instead rely on vpn. Tailscale and ZeroTier are easy to setup.

I prefer k0s, https://k0sproject.io/ .

actually that is not really true - i strongly urge you to try out http://k3s.io/ or https://k0sproject.io/

these are full-fledged, certified k8s distributions that run on raspberry pi as well as all the way in production.

https://www.youtube.com/results?search_query=raspberry+pi+k3...

Right. Flux was a handy little tool[1] that sync'd yaml manifests in git repos to live clusters. The concept was fascinating, and the tool was well done--small and efficient. Easy to learn.

In 2019, they announced they'd be "merging" with argocd[2]. It seems the merge never really took place, and after that they deprecated flux and announced flux2[3].

The sudden changes of course were a little confusing and perhaps not too well communicated.

1: https://github.com/fluxcd/flux

If you are looking at multiple instances of Flux on a cluster which is unmaintained, then most likely you are looking at Flux v1 which is the legacy version and users are all recommended to migrate to the new Flux v2 that has the feature of multiple git repositories and supporting to allow multiple syncs or even multiple tenants.

CI/CD: Tekton Flux

Use ArgoCD or Flux for Kubernetes, and Serverless Stack for your serverless Lambda applications.

HybridK8s Droid - Intelligence foor your favourite Delivery Platform Devtron - Software Delivery Workflow for Kubernetes Skaffold - Easy and Repeatable Kubernetes Development Apollo - Apollo - The logz.io continuous deployment solution over kubernetes Helm Cabin - Web UI that visualizes Helm releases in a Kubernetes cluster flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) Kubeform - Kubernetes CRDs for Terraform providers https://kubeform.com Spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. http://www.spinnaker.io/ werf - GitOps tool to deliver apps to Kubernetes and integrate this process with GitLab and other CI tools Flux - GitOps Kubernetes operator Argo CD - Declarative continuous deployment for Kubernetes Tekton - A cloud native continuous integration and delivery (CI/CD) solution Jenkins X - Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Tekton, Knative, Lighthouse, Skaffold and Helm KubeVela - KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure ksonnet - A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters CircleCI - A cloud-based tool that helps build continuous integration and continuous delivery pipelines to Kubernetes.

Does a tool like this exist? I am aware of the argoCD image updater which is similar but not quite what I’m looking for, and am aware that flux has an old feature request for this https://github.com/fluxcd/flux/issues/2711

The blog post by Weaveworks, which coined the term GitOps in 2017, also names the first GitOps operator: Flux. In the meantime, this has been completely rewritten as Flux v2. In addition to Flux and Flux v2, the associated project "Flux" develops other components. Weaveworks has now handed the project over to the Cloud Native Computing Foundation (CNCF). By now, the project is in the second maturity level: incubator phase.

Here's our GitHub for Weave Flux and an overview of GitOps

Looks really neat. We have a not-super-trivial rails app that I want to move to docker one day, but kinda scared to make the jump. We're already using docker for development, plus even have a home-grown docker-compose setup for ephemeral labs, but it's clunky at best.

This seems like something that might provide a simple jumping board hopefully... Also bumped into fluxCD[0] recently which also looks interesting.

[0] https://github.com/fluxcd/flux

> It doesn't make all the other yaml files happen. It doesn't make the yaml files you no longer want happening, stop happening. It doesn't even tell you "these things were created by 'old' yaml files" and should be garbage collected (since it doesn't seem to have a sense of old yaml files).

This is definitely one piece of Kubernetes that is getting a lot of attention recently. The three tools I've been paying attention to are Argo CD[0], Flux[1], and Config Sync[2].

All of these allow you to point your repository to a cluster and sync resources from the repo to the cluster, including deletes.

[0] https://argoproj.github.io/argo-cd/

[1] https://github.com/fluxcd/flux

[2] https://cloud.google.com/kubernetes-engine/docs/add-on/confi...

Disclaimer: I work at GCP, but not on the GKE team. Opinions are my own.