kubeval VS skaffold

I don't use it myself, but it seems what are you looking for. https://github.com/instrumenta/kubeval

1. Validate Using ValidKube, you can Validate your YAML files. It can help you fix the indentation also add, remove and rearrange things according to the actual YAML and Kubernetes schema. It is available as a open source repository as Kubeval . https://github.com/instrumenta/kubeval

The idea behind Validkube is to fuse together the capabilities of three other popular open-source projects (kubeval, kubectl-neat & trivy) and present them in a single view, providing users with a way to ensure YAML code hygiene and security, in one place, with just a few clicks of the button.

Kubeval - Well known, It only validates against the given Kubernetes Version but doesn’t provide a migration path

Kubeval and kubeconform are command-line tools that were developed with the intent to validate Kubernetes manifests without the requirement of having a running Kubernetes environment. Because kubeconform is based on kubeval, they operate similarly — verification is performed against pre-generated JSON schemas that are created from the OpenAPI specifications (swagger.json) for each particular Kubernetes version. All that remains to run the schema validation tests is to point the tool executable to a single manifest, directory or pattern.

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