fix munge-docs build errors
This commit is contained in:
@@ -21,7 +21,7 @@
|
||||
* There are example files and walkthroughs in the [examples](../examples/)
|
||||
folder.
|
||||
|
||||
* If something went wrong, see the [troubleshooting](troubleshooting.md) document for how to debug.
|
||||
* If something went wrong, see the [troubleshooting](http://kubernetes.io/docs/troubleshooting/) guide for how to debug.
|
||||
You should also check the [known issues for the release](../CHANGELOG.md) you're using.
|
||||
|
||||
* To report a security issue, see [Reporting a Security Issue](reporting-security-issues.md).
|
||||
|
@@ -29,7 +29,7 @@ The criteria for inclusion are as follows:
|
||||
specification, whereas there are countless different systems for definition workflows of dependent actions (e.g. Celery et al.).
|
||||
* The API object is expected to be generally useful to greater than 50% of the Kubernetes users. This is to ensure that we don't build up a collection of niche APIs
|
||||
that users rarely need.
|
||||
* There is general consensus in the Kubernetes community that the API object is in the "Kubernetes layer". See ["What is Kubernetes?"](whatisk8s.md) for a detailed
|
||||
* There is general consensus in the Kubernetes community that the API object is in the "Kubernetes layer". See ["What is Kubernetes?"](http://kubernetes.io/docs/whatisk8s/) for a detailed
|
||||
explanation of what we believe the "Kubernetes layer" to be.
|
||||
|
||||
Of course for every set of rules, we need to ensure that we are not hamstrung or limited by slavish devotion to those rules. Thus we also introduce two exceptions
|
||||
|
@@ -30,7 +30,7 @@ redirect users to Slack. Also check out the
|
||||
In general, try to direct support questions to:
|
||||
|
||||
1. Documentation, such as the [user guide](../user-guide/README.md) and
|
||||
[troubleshooting guide](../troubleshooting.md)
|
||||
[troubleshooting guide](http://kubernetes.io/docs/troubleshooting/)
|
||||
|
||||
2. Stackoverflow
|
||||
|
||||
|
@@ -43,7 +43,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](../troubleshooting.md#slack) and one of the committers will link to it from the wiki.
|
||||
Just file an issue or chat us on [Slack](http://slack.kubernetes.io) and one of the committers will link to it from the wiki.
|
||||
|
||||
## Development Distro Guidelines
|
||||
|
||||
|
Reference in New Issue
Block a user