fleet alternatives and similar packages
Based on the "Other Software" category.
Alternatively, view fleet alternatives based on common mentions on social networks and blogs.
-
-
-
limetext
Open source API-compatible alternative to the text editor Sublime Text -
-
Gor
GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes. -
Seaweed File System
SeaweedFS is a distributed storage system for blobs, objects, files, and data lake, to store and serve billions of files fast! Blob store has O(1) disk seek, local tiering, cloud tiering. Filer supports cross-cluster active-active replication, Kubernetes, POSIX, S3 API, encryption, Erasure Coding for warm storage, FUSE mount, Hadoop, WebDAV. -
croc
Easily and securely send things from one computer to another :crocodile: :package: -
rkt
An App Container runtime that integrates with init systems, is compatible with other container formats like Docker, and supports alternative execution engines like KVM. -
confd
Manage local application configuration files using templates and data from etcd or consul -
Comcast
Simulating shitty network connections so you can build better systems. -
toxiproxy
:alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing -
-
Docker
Notary is a project that allows anyone to have trust over arbitrary collections of data -
scc
Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go -
Juju
Universal Operator Lifecycle Manager (OLM) for Kubernetes operators, and operators for traditional Linux and Windows apps, with declarative integration between operators for automated microservice integration. -
-
Stack Up
Super simple deployment tool - think of it like 'make' for a network of servers -
-
Documize
Modern Confluence alternative designed for internal & external docs, built with Golang + EmberJS -
-
vFlow
Enterprise Network Flow Collector (IPFIX, sFlow, Netflow) from Verizon Media -
GoDNS
A dynamic DNS client tool supports AliDNS, Cloudflare, Google Domains, DNSPod, HE.net & DuckDNS & DreamHost, etc, written in Go. -
peg
Peg, Parsing Expression Grammar, is an implementation of a Packrat parser generator. -
Go Package Store
An app that displays updates for the Go packages in your GOPATH. -
blocky
Fast and lightweight DNS proxy as ad-blocker for local network with many features -
Guora
🖖🏻 A self-hosted Quora like web application written in Go 基于 Golang 类似知乎的私有部署问答应用 包含问答、评论、点赞、管理后台等功能 -
mockingjay
Fake server, Consumer Driven Contracts and help with testing performance from one configuration file with zero system dependencies and no coding whatsoever -
ipe
An open source Pusher server implementation compatible with Pusher client libraries written in GO -
-
-
-
tcpprobe
Modern TCP tool and service for network performance observability. -
Scout APM - Leading-edge performance monitoring starting at $39/month
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of fleet or a related project?
|
Run Linux Software Faster and Safer than Linux with Unikernels
Sponsored
github.com/nanovms
|
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
Sponsored
www.saashub.com
|
README
Deprecation warning
fleet is no longer developed or maintained by CoreOS. After February 1, 2018, a fleet container image will continue to be available from the CoreOS Quay registry, but will not be shipped as part of Container Linux. CoreOS instead recommends Kubernetes for all clustering needs.
The project exists here for historical reference. If you are interested in the future of the project and taking over stewardship, please contact [email protected]
fleet - a distributed init system
fleet ties together systemd and etcd into a simple distributed init system. Think of it as an extension of systemd that operates at the cluster level instead of the machine level.
This project is quite low-level, and is designed as a foundation for higher order orchestration. fleet is a cluster-wide elaboration on systemd units, and is not a container manager or orchestration system. fleet supports basic scheduling of systemd units across nodes in a cluster. Those looking for more complex scheduling requirements or a first-class container orchestration system should check out Kubernetes. The [fleet and kubernetes comparison table][fleet-vs-k8s] has more information about the two systems.
Current status
The fleet project is no longer maintained.
As of v1.0.0, fleet has seen production use for some time and is largely considered stable. However, there are various known and unresolved issues, including [scalability limitations][fleet-scaling] with its architecture. As such, it is not recommended to run fleet clusters larger than 100 nodes or with more than 1000 services.
Using fleet
Launching a unit with fleet is as simple as running fleetctl start:
$ fleetctl start examples/hello.service
Unit hello.service launched on 113f16a7.../172.17.8.103
The fleetctl start command waits for the unit to get scheduled and actually start somewhere in the cluster.
fleetctl list-unit-files tells you the desired state of your units and where they are currently scheduled:
$ fleetctl list-unit-files
UNIT HASH DSTATE STATE TMACHINE
hello.service e55c0ae launched launched 113f16a7.../172.17.8.103
fleetctl list-units exposes the systemd state for each unit in your fleet cluster:
$ fleetctl list-units
UNIT MACHINE ACTIVE SUB
hello.service 113f16a7.../172.17.8.103 active running
Supported Deployment Patterns
fleet is not intended to be an all-purpose orchestration system, and as such supports only a few simple deployment patterns:
- Deploy a single unit anywhere on the cluster
- Deploy a unit globally everywhere in the cluster
- Automatic rescheduling of units on machine failure
- Ensure that units are deployed together on the same machine
- Forbid specific units from colocation on the same machine (anti-affinity)
- Deploy units to machines only with specific metadata
These patterns are all defined using [custom systemd unit options][unit-files].
Getting Started
Before you can deploy units, fleet must be [deployed and configured][deploy-and-configure] on each host in your cluster. (If you are running CoreOS, fleet is already installed.)
After you have machines configured (check fleetctl list-machines), get to work with the [client][using-the-client.md].
Building
fleet must be built with Go 1.5+ on a Linux machine. Simply run ./build and then copy the binaries out of bin/ directory onto each of your machines. The tests can similarly be run by simply invoking ./test.
If you're on a machine without Go 1.5+ but you have Docker installed, run ./build-docker to compile the binaries instead.
Project Details
API
The fleet API uses JSON over HTTP to manage units in a fleet cluster. See the [API documentation][api-doc] for more information.
Release Notes
See the releases tab for more information on each release.
License
fleet is released under the Apache 2.0 license. See the [LICENSE][license] file for details.
Specific components of fleet use code derivative from software distributed under other licenses; in those cases the appropriate licenses are stipulated alongside the code.
*Note that all licence references and agreements mentioned in the fleet README section above
are relevant to that project's source code only.