Abspath fixes
parent
d63d674cde
commit
47576194a2
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
|
@ -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 `<kubernetes>/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:
|
||||
|
||||
|
|
|
@ -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).
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -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!
|
Loading…
Reference in New Issue