spinnaker VS goseaweedfs

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

You can check SeaweedFS https://github.com/chrislusf/seaweedfs

ChubaoFS - distributed file system and object storage Longhorn - Cloud-Native distributed block storage built on and for Kubernetes OpenEBS - Kubernetes native - hyperconverged block storage with multiple storage engines Rook - Storage Orchestration for Kubernetes SeaweedFS - Distributed file system supports read-write many volumes TiKV - Distributed transactional key-value database velero - Backup and migrate Kubernetes applications and their persistent volumes Vitess - Vitess is a database clustering system for horizontal scaling of MySQL kaDalu - A lightweight Persistent storage solution for Kubernetes / OpenShift using GlusterFS in background

seaweedfs - SeaweedFS is a simple and highly scalable distributed file system for small files.

Seaweedfs looks quite promising but its public url uuid is in the form of <32-bit volume, 64-bit file key, 32-bit file cookie>. The volume is probably fixed most of the time, the file key is an incrementing number while the file cookie is random. 32-bit seems too small to prevent guessing.

MinIO team care about an issue if you are paid customer, not for people who use the open source. Indeed MinIO is not even fully S3 compatible with many edge cases and close the issues related to it by saying it’s not a priority.

You might want to look at other options as well like SeaweedFS [0] a POSIX compliant S3 compatible distributed file system.

[0] https://github.com/chrislusf/seaweedfs

SeaweedFS is a fast, distributed storage system for blobs, objects, files and data that stores/serves billions of files. Can transparently integrate with the cloud with both fast local access and elastic cloud storage capacity. Blob store has O(1) disk seek, local and cloud tiering. Filer supports cross-cluster active-active replication, Kubernetes, POSIX, S3 API, encryption, Erasure Coding for warm storage, FUSE mount, Hadoop and WebDAV. chrislusf finds "it is much faster than the 'high performance' Minio."

welcome to help with https://github.com/chrislusf/seaweedfs

(I work on SeaweedFS) How about using SeaweedFS? https://github.com/chrislusf/seaweedfs

With your dedicated server, the latency is consistent, No API/network cost. Extra data can be tiered to S3.

Basically it is a key-file store.

https://github.com/chrislusf/seaweedfs/wiki/Filer-as-a-Key-L...

https://github.com/chrislusf/seaweedfs/wiki/Cloud-Tier

I am working on SeaweedFS. But seriously, use http://github.com/chrislusf/seaweedfs