{"id":13551520,"url":"https://github.com/coreos/fleet","last_synced_at":"2025-09-27T07:31:52.215Z","repository":{"id":11145030,"uuid":"13512328","full_name":"coreos/fleet","owner":"coreos","description":"fleet ties together systemd and etcd into a distributed init system","archived":true,"fork":false,"pushed_at":"2019-02-05T05:49:16.000Z","size":14054,"stargazers_count":2423,"open_issues_count":106,"forks_count":302,"subscribers_count":133,"default_branch":"master","last_synced_at":"2024-09-04T10:58:05.295Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/coreos.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2013-10-11T23:56:38.000Z","updated_at":"2024-08-04T15:57:05.000Z","dependencies_parsed_at":"2022-09-04T06:21:54.065Z","dependency_job_id":null,"html_url":"https://github.com/coreos/fleet","commit_stats":null,"previous_names":["coreos/coreinit"],"tags_count":51,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/coreos%2Ffleet","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/coreos%2Ffleet/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/coreos%2Ffleet/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/coreos%2Ffleet/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/coreos","download_url":"https://codeload.github.com/coreos/fleet/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":234410241,"owners_count":18828166,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-01T12:01:49.767Z","updated_at":"2025-09-27T07:31:42.202Z","avatar_url":"https://github.com/coreos.png","language":"Go","funding_links":[],"categories":["Go","Remote Container Manager / Orchestration","others","Software Packages","Other Software","软件包","Service Management","軟件包","Workload Orchestration \u0026 Scheduling","DevOps Tools"],"sub_categories":["Other Software","Contents","其他软件","Error Monitoring","其他軟件","Middlewares"],"readme":"## \u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e\u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e\u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e Deprecation warning \u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e\u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e\u003cimg src=\"Documentation/achtung.png\" alt=\"WARNING\" width=\"30\" height=\"30\"\u003e\u003ca name=\"deprecation-warning\"\u003e\u003c/a\u003e\nfleet 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](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html).\n\nThe project exists here for historical reference. If you are interested in the future of the project and taking over stewardship, please contact fleet@coreos.com\n\n# fleet - a distributed init system\n\n[![Build Status](https://travis-ci.org/coreos/fleet.png?branch=master)](https://travis-ci.org/coreos/fleet)\n[![Build Status](https://semaphoreci.com/api/v1/coreos/fleet/branches/master/badge.svg)](https://semaphoreci.com/coreos/fleet)\n\nfleet ties together [systemd][coreos-systemd] and [etcd][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.\n\n**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][kubernetes]. The [fleet and kubernetes comparison table][fleet-vs-k8s] has more information about the two systems.\n\n## Current status\n\nThe fleet project is [no longer maintained](#deprecation-warning).\n\nAs of v1.0.0, fleet has seen production use for some time and is largely considered stable.\nHowever, there are [various known and unresolved issues](https://github.com/coreos/fleet/issues), including [scalability limitations][fleet-scaling] with its architecture.\nAs such, it is not recommended to run fleet clusters larger than 100 nodes or with more than 1000 services.\n\n## Using fleet\n\nLaunching a unit with fleet is as simple as running `fleetctl start`:\n\n```sh\n$ fleetctl start examples/hello.service\nUnit hello.service launched on 113f16a7.../172.17.8.103\n```\n\nThe `fleetctl start` command waits for the unit to get scheduled and actually start somewhere in the cluster.\n`fleetctl list-unit-files` tells you the desired state of your units and where they are currently scheduled:\n\n```sh\n$ fleetctl list-unit-files\nUNIT            HASH     DSTATE    STATE     TMACHINE\nhello.service   e55c0ae  launched  launched  113f16a7.../172.17.8.103\n```\n\n`fleetctl list-units` exposes the systemd state for each unit in your fleet cluster:\n\n```sh\n$ fleetctl list-units\nUNIT            MACHINE                    ACTIVE   SUB\nhello.service   113f16a7.../172.17.8.103   active   running\n```\n\n## Supported Deployment Patterns\n\nfleet is not intended to be an all-purpose orchestration system, and as such supports only a few simple deployment patterns:\n\n* Deploy a single unit anywhere on the cluster\n* Deploy a unit globally everywhere in the cluster\n* Automatic rescheduling of units on machine failure\n* Ensure that units are deployed together on the same machine\n* Forbid specific units from colocation on the same machine (anti-affinity)\n* Deploy units to machines only with specific metadata\n\nThese patterns are all defined using [custom systemd unit options][unit-files].\n\n## Getting Started\n\nBefore 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.)\n\nAfter you have machines configured (check `fleetctl list-machines`), get to work with the [client][using-the-client.md].\n\n### Building\n\nfleet 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`.\n\nIf you're on a machine without Go 1.5+ but you have Docker installed, run `./build-docker` to compile the binaries instead.\n\n## Project Details\n\n### API\n\nThe fleet API uses JSON over HTTP to manage units in a fleet cluster.\nSee the [API documentation][api-doc] for more information.\n\n### Release Notes\n\nSee the [releases tab][releases] for more information on each release.\n\n### License\n\nfleet is released under the Apache 2.0 license. See the [LICENSE][license] file for details.\n\nSpecific components of fleet use code derivative from software distributed under other licenses; in those cases the appropriate licenses are stipulated alongside the code.\n\n[api-doc]: Documentation/api-v1.md\n[contributing]: CONTRIBUTING.md\n[coreos-systemd]: https://github.com/coreos/docs/blob/master/os/getting-started-with-systemd.md\n[deploy-and-configure]: Documentation/deployment-and-configuration.md\n[etcd]: https://github.com/coreos/etcd\n[fleet-scaling]: Documentation/fleet-scaling.md\n[fleet-vs-k8s]: Documentation/fleet-k8s-compared.md\n[kubernetes]: http://kubernetes.io\n[license]: LICENSE\n[maintainers]: MAINTAINERS\n[releases]: https://github.com/coreos/fleet/releases\n[unit-files]: Documentation/unit-files-and-scheduling.md#fleet-specific-options\n[using-the-client.md]: Documentation/using-the-client.md\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcoreos%2Ffleet","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcoreos%2Ffleet","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcoreos%2Ffleet/lists"}