The 'user-guide' subdirectory is almost empty now after the contents
are migrated to either concepts or tasks. This PR removes the contents
left over in this path.
* Use Terminated instead of Failed
Containers that terminate successfully (exit code 0) can also be restarted and it's the default behaviour is restartPolicy is not specified.
* Use Exited instead of Failed
In the upstream code base, there are cases where the field description
string contain substrings like '*', 'pods/*', '*/scale' and '*/*'.
When generating reference docs out of these Go comments, the Node.js
module used was incorrectly passing the asterisks as '<em>', i.e. a
mark for emphasize. This behavior has rendered the output documentation
very misleading. For example, in the definition for RuleWithOperations,
users can specify '*' as a wildcard for matching all apiGroups, all
resources. However, the generated docs is showing that an empty string
'' is used to match all apiGroups or resources. This is a serious bug
fixed by this PR.
Doc generator patch is included in PR to
kubernetes-incubator/reference-docs.
* Initial Kubefed AWS Route53 on-prem documentation
* Add flag requirement for kubefed init
* conform to style guidelines
* fix controller-manager wording
* move cut-off section from CoreDNS support
Since the default annotation prefix has been changed to "nginx.ingress.kubernetes.io" in nginx ingress controller, the examples in ingress doc should be updated.
* Document new OpenAPI endpoint
Document new OpenAPI endpoint and deprecation announcement for old endpoints.
* Remove out-of-date swagger spec information
Deprecation announcement is in line 29
* Update default behavior for endpoint HTTP headers
First-time kubeadm user here: The v1.10.0 docs indicate that config file use is experimental, but judging from the comments on https://github.com/kubernetes/kubernetes/pull/59288 it looks like new features are beginning to be supported only in the config file. controlPlaneEndpoint is super useful for us and while I suspect the kubeadm init docs will ultimately be re-written to emphasize the config file options rather than flags (with appropriate examples and descriptions as the flags have now), it would've saved us some time today if we'd seen controlPlaneEndpoint in the config file example.
* Add draft for blog migration post
* Small revisions
* Most important commit ever
* Feedback from kbarnard10
- Turn URLs into hyperlinks
- Remove one line
* Feedback from sarahkconway
- Specify that blog reviews are more transparent/streamlined
* Feedback from kbarnard10, part 2
Added "how to submit a blog post"
Revised "confidentiality"
* Feedback from kbarnard10, part 3
* Renamed file for date accuracy
* Changed date back, added email link