Merge pull request #1726 from ElijahCaine/fleet-deprecation-notice

Dongsu Park · Dongsu Park · commit 39312a2c8e08 · 2017-02-08T10:04:35.000+01:00
Docs: Add fleet deprecation notice to docs.
diff --git a/Documentation/api-v1-alpha.md b/Documentation/api-v1-alpha.md
diff --git a/Documentation/api-v1.md b/Documentation/api-v1.md
@@ -1,5 +1,7 @@
 # fleet API v1
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 The fleet API allows you to manage the state of the cluster using JSON over HTTP.
 
 ## Managing Units
diff --git a/Documentation/architecture.md b/Documentation/architecture.md
@@ -1,5 +1,7 @@
 # Architecture
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 ## fleetd
 
 Every system in the fleet cluster runs a single `fleetd` daemon. Each daemon encapsulates two roles: the *engine* and the *agent*. An engine primarily makes scheduling decisions while an agent executes units. Both the engine and agent use the _reconciliation model_, periodically generating a snapshot of "current state" and "desired state" and doing the necessary work to mutate the former towards the latter.
diff --git a/Documentation/deployment-and-configuration.md b/Documentation/deployment-and-configuration.md
@@ -1,5 +1,7 @@
 # Deploying fleet
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 Deploying `fleet` is as simple as dropping the `fleetd` binary on a machine with access to etcd and starting it.
 
 Deploying `fleet` on CoreOS is even simpler: just run `systemctl start fleet`. The built-in configuration assumes each of your hosts is serving an etcd endpoint at one of the default locations (http://127.0.0.1:2379 or http://127.0.0.1:4001). However, if your etcd cluster differs, you must make the corresponding configuration changes.
diff --git a/Documentation/examples/example-deployment.md b/Documentation/examples/example-deployment.md
@@ -1,5 +1,7 @@
 # Deploying a Service Using fleet
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 The following is an example of how one might deploy a load-balanced web service using fleet.
 This example deploys [subgun][subgun], a simple subscription tool for [mailgun][mailgun].
 
diff --git a/Documentation/examples/service-discovery.md b/Documentation/examples/service-discovery.md
@@ -1,5 +1,7 @@
 # Service Discovery
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 Since applications and networking environments vary widely between customer deployments, fleet does not provide a generalized, integrated solution for service discovery. However, there are a number of patterns available which can easily be implemented on top of fleet to provide automated and reliable service discovery. One such pattern, the _sidekick model_, is described below.
 
 ## Sidekick model
diff --git a/Documentation/rkt_guide.md b/Documentation/rkt_guide.md
@@ -1,5 +1,7 @@
 # Running fleetd under rkt
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 The following guide will show you how to run fleetd under rkt.
 
 ## Building fleet ACI
diff --git a/Documentation/unit-files-and-scheduling.md b/Documentation/unit-files-and-scheduling.md
@@ -1,5 +1,7 @@
 # Unit Files
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 Unit files are the primary means of interacting with fleet. They define what you want to do, and how fleet should do it.
 
 fleet will schedule any valid service, socket, path or timer systemd unit to a machine in the cluster, taking into account a few special properties in the `[X-Fleet]` section. If you're new to using systemd unit files, check out the [Getting Started with systemd guide][systemd-guide].
diff --git a/Documentation/using-the-client.md b/Documentation/using-the-client.md
@@ -1,5 +1,7 @@
 # Using the Client
 
+**[fleet is no longer actively developed or maintained by CoreOS](https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html). CoreOS instead recommends [Kubernetes](https://coreos.com/kubernetes/docs/latest/) for cluster orchestration.**
+
 fleet provides a command-line tool called `fleetctl`. The commands provided by
 `fleetctl` are analogous to those of systemd's CLI, `systemctl`.
 
