diff options
| author | Haoran Wang <haowang@redhat.com> | 2017-04-09 16:41:12 +0800 |
|---|---|---|
| committer | Haoran Wang <haowang@redhat.com> | 2017-04-09 16:43:34 +0800 |
| commit | d237df0b0117db64cd3b616ca0f54d0e8f671a5b (patch) | |
| tree | aa0c4afa7498ee28989b2ba31caba5c4c2a67b76 | |
| parent | 0df052a403e0effd4efea1616a55ecacb927ea1c (diff) | |
fix link of multiple-scheduler
| -rw-r--r-- | contributors/devel/mesos-style.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/mesos-style.md b/contributors/devel/mesos-style.md index 81554ce8..53ee139e 100644 --- a/contributors/devel/mesos-style.md +++ b/contributors/devel/mesos-style.md @@ -61,7 +61,7 @@ machine manages the collection during their lifetimes Out-of-the-box Kubernetes has *workload-specific* abstractions (ReplicaSet, Job, DaemonSet, etc.) and corresponding controllers, and in the future may have -[workload-specific schedulers](../../docs/proposals/multiple-schedulers.md), +[workload-specific schedulers](../design-proposals/multiple-schedulers.md), e.g. different schedulers for long-running services vs. short-running batch. But these abstractions, controllers, and schedulers are not *application-specific*. |