skaffold

Issue in question: https://github.com/GoogleContainerTools/skaffold/issues/5210

Something like IAM seems necessary to authorize fork PRs to pull from but not push to registries: https://github.com/GoogleContainerTools/skaffold/issues/4432 in order to rate limit unauthenticated pulls: https://docs.docker.com/docker-hub/download-rate-limit/

Full-disclosure: I co-founded a company that's building a developer tool for K8s (and distributed systems in general). But we've had a lot of success with running on GKE. The tool that we're making takes away the complexity of building, testing and deploying the stack, and GKE takes care of running it. In fact we use GKE for both our development and staging/prod environments. There are a lot of great tools out there that vastly improve the K8s developer experience[1] and the cloud providers take away of the pain of operating it. And with tools like Terraform and Pulumi you can codify the whole setup. Here's an example of how you can quite easily get started on GKE: https://medium.com/garden-io/gke-and-cloud-sql-a-complete-wo... Here's a video of the same workflow: https://www.youtube.com/watch?v=iHyeD97GrE4. [1] https://github.com/GoogleC

Seems similar to skaffold: https://github.com/GoogleContainerTools/skaffold

There are some nice open-source projects out there for getting started with distributed systems (full disclosure, I'm a co-founder of one of them). They all abstract away (what some may call) the boring bits of getting started with distributed systems, like plumbing and such, and in general aim to improve the overall developer experience. In no particular order: https://github.com/GoogleContainerTools/skaffold https://github.com/garden-io/garden https://github.com/windmilleng/tilt

There are at least two options that work with helm, google's skaffold (https://github.com/GoogleContainerTools/skaffold) and microsoft's draft (https://github.com/Azure/draft). The former supports helm along with kustomize and just plain old kubectl yaml files, draft seems to be tied to helm. Personally I have used skaffold with success, and draft paniced on me so I stopped playing with it.

We have the entire development environment in Kubernetes. IDE is only used for code editing, which is then synced to the cluster. Auto-generated code and node_modules are synced back for code completion. That way, everyone has an identical dev environment and we don't depend on any particular IDE (want to use Emacs? sure). No setup steps, just running one script to create a new namespace with all applications running inside. Broke it, messed up an upgrade? Just destroy and redeploy. We hacked Arcanist[1] to run linters in the cluster. Modified a TypeScript file? "arc lint" will make sure your TypeScript pod is up-to-date and run the linter there, etc. We're using custom tooling which is faster than https://github.com/GoogleContainerTools/skaffold, but it's the same approach. Thinking about open sourcing it. [1]: Phabricator's CLI client

1. This is something I've found a bit painful, too -- this looks helpful: https://github.com/GoogleContainerTools/skaffold 2. Haven't tried this, but I'm aware of it - does this address your point here ? https://www.telepresence.io/ 3. Something like this? https://github.com/rycus86/docker-pycharm I agree that this could be very cool if further developed. I agree that we'll start to see deeper integration across the development environment though, as more dev-hours are spent on building up the toolchain.

Jenkins X runs in containers on kubernetes and all the builds are done in containers. You can use whatever pod template (collection of docker images) in your CI/CD pipeline: http://jenkins-x.io/architecture/pod-templates/ Yes we can support things like parallel steps & tests spinning up separate clusters, namespaces or environments (we do this ourselves to test Jenkins X). We delegate to an OSS tool called Skaffold to actually build docker containers that gives us the flexibility to use different approaches for docker image creation (e.g. kaniko or Google Container Builder or use the local docker daemon etc) https://github.com/GoogleContainerTools/skaffold Using Kubernetes as an engine for orchestrating containers works very well - thats kinda what Kubernetes was designed for. Though you are free to extend & integrate tools like ActiveMQ

Agreed! Jenkins X uses Skaffold to do the docker image building so can be configured to use kaniko or Google Container Builder etc https://github.com/GoogleContainerTools/skaffold

Google released a tool to help with continuous deployments called skaffold [1]. Haven't used it myself (just using bitbucket pipelines) but looks like it's a relevant tool to this. Nice. [1]: https://github.com/GoogleCloudPlatform/skaffold