Content deleted Content added
Citation bot (talk | contribs) Add: date. | Use this bot. Report bugs. | Suggested by Spinixster | Category:Linux distributions | #UCB_Category 34/338 |
m Fix casing |
||
Line 324:
| date = January 15, 2014 | access-date = February 13, 2014
| author = Brandon Philips | website = speakerdeck.com
}}</ref>
Container Linux also provides the {{Mono|fleet}} cluster manager which controls Container Linux's separate systemd instances at the cluster level. As of 2017 "fleet" is no longer actively developed and is deprecated in favor of [[Kubernetes]].<ref>{{cite web|last1=Wood|first1=Josh|title=Container orchestration: Moving from fleet to Kubernetes|url=https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html|website=coreos..com|publisher=CoreOS}}</ref> By using {{Mono|fleetd}}, Container Linux creates a distributed [[init|init system]] that ties together separate systemd instances and a cluster-wide {{Mono|etcd}} deployment;<ref name="lwn-617452" /> internally, {{Mono|fleetd}} daemon communicates with local {{Mono|systemd}} instances over [[D-Bus]], and with the {{Mono|etcd}} deployment through its exposed API. Using {{Mono|fleetd}} allows the deployment of single or multiple [[Software container|containers]] cluster-wide, with more advanced options including [[Redundancy (engineering)|redundancy]], [[failover]], deployment to specific cluster members, dependencies between containers, and grouped deployment of containers. A command-line utility called {{Mono|fleetctl}} is used to configure and monitor this distributed init system;<ref>{{Cite web
| |||