devspace VS skaffold

There is actually a built-in converter from docker-compose.yaml to devspace.yaml, it is part of the "devspace init" command. There are a few known issues related to it, in case you would like to contribute :)

We’re excited to announce that DevSpace version 6 has been released. Thanks to everyone who used the alpha and beta versions and gave us feedback.

You can find the configuration reference for DevSpace 6 in the docs. You can also see the release notes for more details about what’s in the release, including breaking changes in the new config format.

Awesome work on the launch!. I was wondering what the main difference between Nimbus and something like https://devspace.sh/ is?

DevSpace is free, lets you develop natively in the cloud on any K8s cluster. Compatible with any multitenancy solution, policy governance, etc. Works with your IDE of choice. Declarative configuration. Supports custom pipelines and deploy logic. Can link multiple environments together. https://devspace.sh/

Lastly if you are using compose to both build and launch containers then you're going to need more advanced tooling like devspace or skaffold to assist in creating a better development workflow for kubernetes.

$ devspace init ____ ____ | _ \ _____ __/ ___| _ __ __ _ ___ ___ | | | |/ _ \ \ / /\___ \| '_ \ / _` |/ __/ _ \ | |_| | __/\ V / ___) | |_) | (_| | (_| __/ |____/ \___| \_/ |____/| .__/ \__,_|\___\___| |_| ? How do you want to deploy this project? [Use arrows to move, type to filter] > helm: Use Component Helm Chart [QUICKSTART] (https://devspace.sh/component-chart/docs) helm: Use my own Helm chart (e.g. local via ./chart/ or any remote chart) kubectl: Use existing Kubernetes manifests (e.g. ./kube/deployment.yaml) kustomize: Use an existing Kustomization (e.g. ./kube/kustomization/)

I want to be able to clone my repo and just build and deploy my code. I use Devpace to do this (Skaffold another option). This is my alternatove to Docker Compose and in complex microservice environments it can clone and deploy other teams code (as dependencies)

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.

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

To access you service your have several options (it depends on teams the preferences) you can use scaffold https://skaffold.dev/ or for simple case kfwd https://github.com/GiGurra/kfwd. Last for everything that is normally expose on internet you would have an Ingress and use external-dns as you would in prod.

This approach works great when it’s feasible, which is usually at a very early stage in the life of the application where it’s still small and tenable. There’s some tooling that lets you extend this honeymoon phase by letting you do it more easily, like docker-compose, Skaffold, or Tilt. However, at a certain point, even if you’ve written whatever scriptage is needed to actually configure and run the latest stable version of all of your components together, you’re going to hit some sort of ceiling: if you’ve got a large database, or some CPU-heavy computations, or you’re relying on some managed service that can’t be containerized, this approach soon becomes untenable.

Another dev optimization is the conditional rebuilding of a container. For example tools like devspace and skaffold support syncing filles which have changes, but which don't require recompiling.

I have been using Skaffold to deploy my apps to Kubernetes. As I use this for spring Boot apps too so it saves me learning another deployment process.

I really like https://skaffold.dev/ for local development, speeds up repetitive commands I have to run like build/push/apply.