carvel VS skaffold

You should take a look at Carvel maybe something in it could match with your needs.

There's a third option that's quickly rising in popularity, which is Carvel, works great for smaller teams, and allows progressive adoption since it can start as CLI for newer teams learning about gitops concepts.

Carvel (carvel.dev) — featured in opening keynotes.

Huge fan of Carvel tools, it's a whole bunch of them that can help with a wide array of use cases, grab one or two of them for a given scenario, or adopt a bunch that string together to solve larger problems.

+1 been using ytt and kapp, the Carvel stuff in its entirety is a much better experience than helm (it can keep helm to help migration, or deal with the fact everyone still distributes in helm).

Creating Carvel Community which :

https://carvel.dev (and especially the [KAPP](https://carvel.dev/kapp/) piece) is a set of excellent tools to level up on Kubernetes.

Take a look at Kapp on https://carvel.dev/ for this, possibly.

Hopefully this post has helped you make install process smoother, smarter, and made you discover CARVEL tools.

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