From 47576194a26c09cd03f9c3c250242e29be5ca967 Mon Sep 17 00:00:00 2001 From: John Mulhausen Date: Thu, 18 Feb 2016 19:59:58 -0800 Subject: [PATCH] Abspath fixes --- v1.1/docs/admin/daemons.md | 2 +- v1.1/docs/devel/writing-a-getting-started-guide.md | 2 +- v1.1/docs/getting-started-guides/docker-multinode/master.md | 2 +- v1.1/docs/getting-started-guides/docker-multinode/testing.md | 2 +- v1.1/docs/getting-started-guides/gce.md | 2 +- v1.1/docs/user-guide/debugging-services.md | 2 +- v1.1/docs/user-guide/deployments.md | 2 +- v1.1/docs/user-guide/jobs.md | 2 +- v1.1/docs/user-guide/persistent-volumes/index.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/v1.1/docs/admin/daemons.md b/v1.1/docs/admin/daemons.md index 3f7871f35c..610a0fa250 100644 --- a/v1.1/docs/admin/daemons.md +++ b/v1.1/docs/admin/daemons.md @@ -158,7 +158,7 @@ all or certain hosts, and when it needs to start before other pods. ## Caveats -DaemonSet objects are in the [`extensions` API Group](/{{page.version}}/docs/api/)#api-groups). +DaemonSet objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups). DaemonSet is not enabled by default. Enable it by setting `--runtime-config=extensions/v1beta1/daemonsets=true` on the api server. This can be achieved by exporting ENABLE_DAEMONSETS=true before running kube-up.sh script diff --git a/v1.1/docs/devel/writing-a-getting-started-guide.md b/v1.1/docs/devel/writing-a-getting-started-guide.md index 5c2df77204..6ab66166c8 100644 --- a/v1.1/docs/devel/writing-a-getting-started-guide.md +++ b/v1.1/docs/devel/writing-a-getting-started-guide.md @@ -46,7 +46,7 @@ These guidelines say *what* to do. See the Rationale section for *why*. If you have a cluster partially working, but doing all the above steps seems like too much work, we still want to hear from you. We suggest you write a blog post or a Gist, and we will link to it on our wiki page. -Just file an issue or chat us on [Slack](/{{page.version}}/docs/troubleshooting/)#slack) and one of the committers will link to it from the wiki. +Just file an issue or chat us on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and one of the committers will link to it from the wiki. ## Development Distro Guidelines diff --git a/v1.1/docs/getting-started-guides/docker-multinode/master.md b/v1.1/docs/getting-started-guides/docker-multinode/master.md index ace22aa476..386d270496 100644 --- a/v1.1/docs/getting-started-guides/docker-multinode/master.md +++ b/v1.1/docs/getting-started-guides/docker-multinode/master.md @@ -171,7 +171,7 @@ NAME LABELS STATUS ``` If the status of the node is `NotReady` or `Unknown` please check that all of the containers you created are successfully running. -If all else fails, ask questions on [Slack](/{{page.version}}/docs/troubleshooting/)#slack). +If all else fails, ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack). ### Next steps diff --git a/v1.1/docs/getting-started-guides/docker-multinode/testing.md b/v1.1/docs/getting-started-guides/docker-multinode/testing.md index fd6dabce03..71fb3056fc 100644 --- a/v1.1/docs/getting-started-guides/docker-multinode/testing.md +++ b/v1.1/docs/getting-started-guides/docker-multinode/testing.md @@ -15,7 +15,7 @@ NAME LABELS STATUS 127.0.0.1 kubernetes.io/hostname=127.0.0.1 Ready ``` -If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on [Slack](/{{page.version}}/docs/troubleshooting/)#slack). +If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on [Slack](/{{page.version}}/docs/troubleshooting/#slack). ### Run an application diff --git a/v1.1/docs/getting-started-guides/gce.md b/v1.1/docs/getting-started-guides/gce.md index bebf740caa..37a390b383 100644 --- a/v1.1/docs/getting-started-guides/gce.md +++ b/v1.1/docs/getting-started-guides/gce.md @@ -54,7 +54,7 @@ cluster/kube-up.sh If you want more than one cluster running in your project, want to use a different name, or want a different number of worker nodes, see the `/cluster/gce/config-default.sh` file for more fine-grained configuration before you start up your cluster. If you run into trouble, please see the section on [troubleshooting](gce/#troubleshooting), post to the -[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting/)#slack). +[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack). The next few steps will show you: diff --git a/v1.1/docs/user-guide/debugging-services.md b/v1.1/docs/user-guide/debugging-services.md index 0dd6390084..9488ec2e53 100644 --- a/v1.1/docs/user-guide/debugging-services.md +++ b/v1.1/docs/user-guide/debugging-services.md @@ -494,7 +494,7 @@ misbehaving. And yet your `Service` is not working. You should probably let us know, so we can help investigate! Contact us on -[Slack](/{{page.version}}/docs/troubleshooting/)#slack) or +[Slack](/{{page.version}}/docs/troubleshooting/#slack) or [email](https://groups.google.com/forum/#!forum/google-containers) or [GitHub](https://github.com/kubernetes/kubernetes). diff --git a/v1.1/docs/user-guide/deployments.md b/v1.1/docs/user-guide/deployments.md index acbfa85604..3dd853f276 100644 --- a/v1.1/docs/user-guide/deployments.md +++ b/v1.1/docs/user-guide/deployments.md @@ -19,7 +19,7 @@ A typical use case is: ## Enabling Deployments on kubernetes cluster -Deployments is part of the [`extensions` API Group](/{{page.version}}/docs/api/)#api-groups) and is not enabled by default. +Deployments is part of the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups) and is not enabled by default. Set `--runtime-config=extensions/v1beta1/deployments=true` on API server to enable it. This can be achieved by exporting `ENABLE_DEPLOYMENTS=true` before running diff --git a/v1.1/docs/user-guide/jobs.md b/v1.1/docs/user-guide/jobs.md index 1eb43ec6b2..3439cb22a9 100644 --- a/v1.1/docs/user-guide/jobs.md +++ b/v1.1/docs/user-guide/jobs.md @@ -198,7 +198,7 @@ value is `Always`.) ## Caveats -Job objects are in the [`extensions` API Group](/{{page.version}}/docs/api/)#api-groups). +Job objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups). Job objects have [API version `v1beta1`](/{{page.version}}/docs/api/)#api-versioning). Beta objects may undergo changes to their schema and/or semantics in future software releases, but diff --git a/v1.1/docs/user-guide/persistent-volumes/index.md b/v1.1/docs/user-guide/persistent-volumes/index.md index ad065c4d66..8ecc330665 100644 --- a/v1.1/docs/user-guide/persistent-volumes/index.md +++ b/v1.1/docs/user-guide/persistent-volumes/index.md @@ -88,6 +88,6 @@ $ curl 10.0.0.241:3000 I love Kubernetes storage! ``` -Hopefully this simple guide is enough to get you started with PersistentVolumes. If you have any questions, join the team on [Slack](/{{page.version}}/docs/troubleshooting/)#slack) and ask! +Hopefully this simple guide is enough to get you started with PersistentVolumes. If you have any questions, join the team on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and ask! Enjoy! \ No newline at end of file