spinnaker VS okteto

Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:44:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:33:17Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"} I tried to launch spinnaker pods(yaml files here). I choose Flannel(kubectl apply -f kube-flannel.yml) while installing K8. Then I see the pods are not starting, it is struck in "ContainerCreating" status. I kubectl describe a pod, showing NetworkPlugin cni failed to set up pod

The project (https://github.com/spinnaker/spinnaker) seems kinda dead. It's supposed to be a CD system, but if one is using something like GitLab (with its own CI/CD) does it make sense?

So, do you use Spinnaker? If not, what do you use instead?

I was following this documentation to setup Spinnaker on Kubernetes. I ran the scripts as they specified. Then the replication controllers and services are started. But some of PODs are not started

From a workflow perspective, developers push their code to a code repository and then manually trigger a pipeline with tools such as Gitkube or Spinnaker that deploys the code in a Kubernetes environment, usually in a remote cluster in the cloud.

HybridK8s Droid - Intelligence foor your favourite Delivery Platform Devtron - Software Delivery Workflow for Kubernetes Skaffold - Easy and Repeatable Kubernetes Development Apollo - Apollo - The logz.io continuous deployment solution over kubernetes Helm Cabin - Web UI that visualizes Helm releases in a Kubernetes cluster flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) Kubeform - Kubernetes CRDs for Terraform providers https://kubeform.com Spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. http://www.spinnaker.io/ werf - GitOps tool to deliver apps to Kubernetes and integrate this process with GitLab and other CI tools Flux - GitOps Kubernetes operator Argo CD - Declarative continuous deployment for Kubernetes Tekton - A cloud native continuous integration and delivery (CI/CD) solution Jenkins X - Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Tekton, Knative, Lighthouse, Skaffold and Helm KubeVela - KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure ksonnet - A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters CircleCI - A cloud-based tool that helps build continuous integration and continuous delivery pipelines to Kubernetes.

Spinnaker

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

Check also devspace.sh and okteto.com

You can consider using okteto for development environments, it lets you deploy your local code directly to k8s replacing the existing pods, our team uses it and it works pretty well with Golang.

Okteto is an application that allows you to develop inside a container, along with many features it permit the user to start a development environment and provide an automatic SSL Endpoints for k8s.

With Infrastructure as Code at its current state of maturity, it’s now easier than ever to replicate microservice environments in the cloud. This unlocked a new approach of having a personal production-like cloud environment for every developer, which they can use freely and in isolation. It comes in two flavors - persistent environments, or ephemeral environments created on demand with products like Okteto or Bunnyshell (also sometimes called Environment as a Service)1. This approach overcomes the resource limitations of the local environment but substitutes them for some new difficulties:

Remote development will be popular? Yes.

But developing in a monolithic machine may be not. The development environment should be clean and isolated, and products like gitpod and coder is promising.

Besides this, maybe you can have a look at https://github.com/tensorchord/envd and https://github.com/okteto/okteto

Okteto accelerates the development workflow of Kubernetes applications. You write your code locally and okteto detects the changes and instantly updates your Kubernetes applications.

Hey! Recently, I’ve been playing around with [Okteto](https://www.okteto.com/) to see how it helps with the local development of apps that will run in Kubernetes. It seems to be quite a good option for developers who don’t want to spend their time dealing with setting up and maintaining clusters. Moreover, you can use a development environment from Okteto without thinking about CI/CD pipelines for delivering the app.So, instead of working on your code locally and deploying it then to the cluster, the whole development process is shifted straight to K8s. That makes Okteto approach a bit different from what other projects, like Skaffold and werf, do. To implement this idea, they offer a [CLI tool](https://github.com/okteto/okteto) and their own cloud provided as both SaaS and self-hosted (it has a limited free option).Here is [my overview](https://blog.flant.com/okteto-cloud-for-local-development-in-kubernetes/) of Okteto; any feedback — especially, your own experience — is more than welcome.

There's a long long route to cloudification, but works like Okteto[1] seem like a nice early pass at doing what Docker-Compose was capable of for fast local development, but modern. Pursuing remote-development makes a lot of sense. There's already solid VSCode integration[2].

If you just need a terminal like thing to local-dev in, toolbx[3] is probably the first choice.

[1] https://github.com/okteto/okteto

[2] https://marketplace.visualstudio.com/items?itemName=okteto.r...

[3] https://containertoolbx.org/

Hi Jacob. I am one of the founders of Okteto (https://okteto.com/), a remote development platform for Compose and Kubernetes applications. We use Syncthing to sync code between the developer laptop and pods running in Kubernetes. I would love to know your thoughts on the strengths and weak points of Mutagen vs Syncthing for this use case.