awesome-k8s-resources VS skaffold

Kubernetes: https://github.com/tomhuang12/awesome-k8s-resources

Navigating this vast expanse of options can be overwhelming when deciding which tools to incorporate into your projects. Tom Huang contributes to the solution by meticulously curating an awesome list of Kubernetes tools and resources, categorizing and ranking each Kubernetes application with traction based on GitHub stars.

There are some lists already: * https://github.com/ramitsurana/awesome-kubernetes * https://github.com/tomhuang12/awesome-k8s-resources

Not anything found on the awesome k8s resources list but for example:

A much more comprehensive list can be found here. This is likely a subset of the items in that repo and a few additions of tools i’ve tried out or want to try out to make my K8s life easier.

For other useful tools, please check out my curated list: https://github.com/tomhuang12/awesome-k8s-resources

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