skaffold VS flux2

A nice middle ground is using a tool like Google's Skaffold, which provides "Bazel-like" capabilities for composing Docker images and tagging them based on a number of strategies, including file manifests. In my case, I also use build args to explicitly set versions of external dependencies.

While I am in a Typescript environment with this setup at the moment, my personal experience that Skaffold with Docker has a lighter implementation and maintenance overhead than Bazel. (You also get the added benefit of easy deployment and automatic rebuilds.)

I quite liked using Bazel in a small Golang monorepo, but I ran into pain when trying to do things like include third-party pre-compiled binaries in the Docker builds, because of the unusual build rules convention. The advantage of Skaffold is it provides a thin build/tag/deploy/verify layer over Docker and other container types. Might be worth a look!

Kudos to the Google team building it! https://skaffold.dev

To get a similar experience of preevy up, first we’ll need to split the build and deploy using process or alternatively employ tools that orchestrate build-tag-push-update-sync flow like Skaffold/Tilt.

We will be using docker and microk8s from Canonical. For running our software during development, we will be using skaffold which is a great tool developed by Google.

To add more context, if you are developing containers in a local dev environment, the minimum you should have is the Google Cloud SDK and Skaffold. The SDK will allow you to programmatically interact with Googleapis e.g. auth, services, resources. Skaffold will allow you to build and deploy to the cloud similar to working with a local dev environment.

I have used both Skaffold and Devspace. I prefer the latter.

I wonder if it has some overlap with https://skaffold.dev/.

K3d and Skaffold for local development

skaffold.dev - build in k8s - no more asking for the database password. All the plumbing to the backend is just done so it's easier for them to test and demo any branch

For those seeking a GitOps-based approach to managing cluster configuration and workloads, EKS Blueprints offers the means to bootstrap a cluster with Argo CD and any number of Argo CD application resources. Additionally, support for Flux is also on the roadmap, expanding the options available for GitOps-based management.

Flux CD is a continuous delivery (CD) tool that automates GitOps-powered app deployments to Kubernetes clusters. It allows you to automate Kubernetes app deployments each time you change your code.

Flux CD, with its Flagger component, provides another automated progressive delivery experience that acts as an alternative to Argo Rollouts. It integrates with popular service mesh solutions, including Istio and Linkerd, to offer simplified blue-green deployments without the hands-on management of Kubernetes Services.

The open source projects Fastly uses and the foundations we partner with are vital to Fastly’s mission and success. Here's an unscientific list of projects and organizations supported by the Linux Foundation that we use and love include: The Linux Kernel, Kubernetes, containerd, eBPF, Falco, OpenAPI Initiative, ESLint, Express, Fastify, Lodash, Mocha, Node.js, Prometheus, Jenkins, OpenTelemetry, Envoy, etcd, Helm, osquery, Harbor, sigstore, cert-manager, Cilium, Fluentd, Keycloak, Open Policy Agent, Coalition for Content Provenance and Authority (C2PA), Flux, gRPC, Strimzi, Thanos, Linkerd, Let’s Encrypt, WebAssembly. And the list goes on!

#cloud-config runcmd: - export GITHUB_TOKEN=${github_token} - export HOME=/root - export XDG_CONFIG_HOME=/root/.config - curl -sfL https://get.k3s.io | sh - # install k8s - export KUBECONFIG=/etc/rancher/k3s/k3s.yaml - until nc -z localhost 6443; do sleep 1; done # wait until k8s is live - curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash # get helm - curl -s https://fluxcd.io/install.sh | sudo bash - kubectl apply -f https://github.com/fluxcd/flux2/releases/latest/download/install.yaml --validate=false - flux bootstrap github --owner=gurghet --repository=wordpress-in-a-jar --branch=master --path=./flux/manifests

Flux CD provides a toolkit of components for implementing GitOps-powered continuous delivery to your Kubernetes clusters. Similarly to ArgoCD, it automatically reconciles your cluster's state to your Git repositories and other sources, while preventing drift.

I decided to use Terraform to manage my K8 resources. I know that there are probably better ways of doing this (like Argo CD or Flux CD), but I ended up settling with Terraform as I was already familiar with the tool and it allowed me to achieve the goal of trying out K8s without being bogged down too much on the deployment process.

Bart: Cert Manager and Argo are popular choices, especially in the GitOps domain. What about Flux?