gefyra VS skaffold

Gefyra attempts to provide the same value as mirrord, but in a different way (via VPN).

Please find the draft here: https://github.com/gefyrahq/gefyra/issues/353

- https://gefyra.dev/

We recently presented our open-source tool Gefyra (https://gefyra.dev) at a "Kubernetes Community Days" event.

My team and I created the open-source tool Gefyra: https://github.com/gefyrahq/gefyra

Gefyra - a tool that creates local infrastructure to write code directly in a Kubernetes cluster while using conventional development tools (including debugger): https://gefyra.dev

As an example: for another project (https://gefyra.dev) I create a Deckfile which contains: - a Keycloak, with initial data (realm, clients, user, etc.) - a service with a sidecar pattern (oauth2-proxy for handling OIDC) - the K8s dashboard for developer experience Have a look: https://github.com/gefyrahq/gefyra-demos/blob/main/deck.yaml And all it takes to run this locally is deck get https://github.com/gefyrahq/gefyra-demos.git Epinio can effectively become part of the Deckfile (so the platform is installed locally already), and the developer can run epinio push immediately after deck get... to bring in new apps. Sounds good.

Mhh. Interesting. With Gefyra (https://gefyra.dev) I automated just that process and it seems to work. I tested it successfully with GKE. However, I decided to use a NodePort service. Is your GCP firewall rule UDP based (TCP is default and does not work)?

If a local Docker container instance supports GPU access on M1 Mac (and I really don't know) you could use Gefyra (https://gefyra.dev) to run the container with the special hardware requirements on you local Docker host and the rest within Minikube. The container running with Gefyra should behave as it would run within a Kubernetes namespace.

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