skaffold VS telepresence

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.

You might want to take a look at https://skaffold.dev/

Because these components are configured as Custom Resource Definitions on Kubernetes, you can create highly reusable pipelines, and Tekton is also compatible with Jenkins, Skaffold, Knative, and other CI/CD tools. Let’s take a look at getting started with Tekton, and start working on building our pipeline.

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.

- Advanced features like profiles and modules for supporting multiple environments

https://skaffold.dev/

Depending on the context, the type of code you do, you may want to also look into the sister protocol to LSP, DAP—debug adaptor protocol. It really depends on your context whether local dev, dev against a remote server, and if the latter whether you run under GCP and thus have the “Snapshot Debugger”, or under Kubernetes with something like Ambassadar/Emissary and thus can run Telepresence, whether you do local or remote Docker and thus most IDEs don't necessarily magically work especially if the containers are competently locked down, etc.

If you're on Kubernetes remotely, Telepresence [0] might be worth a look.

[0] https://www.telepresence.io

This seems to be very similar to Telepresence, which I just couldn't get to work for us.

I think you might be looking for a tool called Telepresence, which can insert a local process into the kubernetes internal network.

What the difference with okteto and telepresence ?

The tool is based on telepresence. It is used at Flare Systems to keep our development setup light and still be able to quickly connect our test apps to a more realistic “staging” environment.

How does this compare to Telepresence? https://www.telepresence.io/

At my company, we're using k8s for basically everything. "Local development" is literally just "run the binary on your local machine" and have everything else run in the cloud, then use Telepresence to bridge the networking gap between your local machine and the cluster.

Debug - difference between local and dev environments: Replicating bugs from remote environments to local is tough. Tools like devspace and telepresence help. The former enables a quick build loop between the local and the remote k8s environment and can be massively helpful in reducing development time. The latter is a lot more magic, directing remote traffic to your local laptop, but is more complex to work with.