skaffold VS devspace-plugin-loft

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

I'm biased but I do think what you're describing is a good use case for Kubernetes. I work for Loft Labs, we're the company that created vcluster. We do have a commercial product called Loft that lets you manage vclusters and offer them self-service to developers. If you want to get more info on that, the web site is loft.sh.

There are some products available, for example Loft who open sourced vcluster

We run on EKS and use https://loft.sh/ to deploy development environments. The engineer runs the single service locally that they want to modify. Any other services or databases that service connects to run remotely in our Development EKS cluster using Loft and port forwards to the engineers local environment.

Lastly, one day my employer will let my run Loft so that I can provide on-demand ephemeral k8s clusters to my dev + test teams.

Have a look at https://github.com/loft-sh/kiosk and maybe the paid version https://loft.sh/

How many friends? I would recommend evaluating Loft which is free for up to 3 users.

Automate the setup of new k8s environments, ideally they should be ephemeral, disposed regularly and rebuilt by the devs themselves, on demand. This will also keep costs in check, devs don't work 24/7 so why should their cloud infrastructure? A tool worth checking would be Loft

Loft solves this + much more. There are cost-saving features too, so it might actually pay for itself. Don't hesitate to book a demo.

Loft.sh provides self-serve Kubernetes solutions for cost optimization, CI/CD, policy enforcement, user management, collaboration, and more. It helps save on Kubernetes costs by using quotas and space constraints which helps while sharing your clusters among multiple users and teams. Auto delete for idle namespaces and sleep mode for idle workloads also saves costs.