TopGit theo dõi coreos/fleet trên GitHub, đã đạt 2.4k sao. fleet ties together systemd and etcd into a distributed init system
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
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 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 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.
Getting Started
Before you can deploy units, fleet must be deployed and configured 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.
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 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 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.
coreos/fleet có 2.4k sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/coreos/fleet. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
coreos/fleet có phải mã nguồn mở không?
Có — coreos/fleet phát hành theo license Apache-2.0, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/coreos/fleet.
coreos/fleet còn đang phát triển không?
Commit gần nhất trên coreos/fleet là 7.8 năm trước (theo timestamp GitHub). Repo có 296 fork — một chỉ báo về mức độ quan tâm của cộng đồng.
coreos/fleet là gì?
coreos/fleet (coreos/fleet) là dự án Go trên GitHub. Theo mô tả gốc: fleet ties together systemd and etcd into a distributed init system
Đọc thêm về coreos/fleet ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/coreos/fleet là nguồn chính thức.
Đọc đầy đủ README ở tab phía trên.
Chưa chắc fleet có hợp với bạn?
Để ChatGPT, Claude hoặc Perplexity tìm hiểu giúp — bấm bên dưới và xem AI nói gì về fleet.