- Added a missing full stop.
- Separated the details on the --type flag under the respective section.
- Linked to the page on setting up Minikube locally.
- Introduced the VM abbreviation when used for the first time on the page.
In AWS cloud platform, omitting the name while initializing etcd cluster
causes "Couldn't find local name "$HOSTNAME in the initial cluster configuration"
It seems that the etcd tries to find short hostname, not the FQDN hostname.
To avoid this, passing the name explicitly to etcd configuration solved the problem.
[related issue1](https://github.com/coreos/bugs/issues/2054)
[related issue2](https://github.com/kubernetes/kubeadm/issues/653)
- The intro section had repeated text on visiting the community page. Refactored this content.
- Minor changes to content.
- Added links to Slack and the SIG docs mailing list.
* Copy-edit based on the style guide
Made the following changes:
- Used present tense.
- Removed latin phrases
- {{< tab name=“Content File #1” include=“example1” />}} was not shown as code. Updated it.
- Copy-edited the description for include under Tabs.
* Updated the text based on the comments
When starting minikube with
`--extra-config=apiserver.Authorization.Mode=RBAC`, the apiserver
container exits with the following error:
```
error: unknown flag: --Authorization.Mode
```
Starting it with `--extra-config=apiserver.authorization-mode=RBAC`
instead fixes the issue.
The first step of [1], kubeadm is necessary to be upgraded because we
need to run kubeadm upgrade plan. Then, the line shows `upgrade kubeadm:`.
However, the commandline contains kubelet also. That seens copy&paste
mistake and unnecessary. This removes it.
In addition, the format of another tab is broken. This fixes it also by
naming another tab.
[1]: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-12/#upgrade-the-control-plane
The current document had a minor issue: " Ask for sponsorship in the #sig-docs channel on the Kubernetes Slack instance](https://kubernetes.slack.com) "
I am assuming you wanted to link #sig-docs channel on the Kubernetes Slack instance to https://kubernetes.slack.com. Therefore, corrected it.
We receive a lot of customer queries around HPA not communicating with metrics-server where the core issue is that metrics-server is not installed. Feedback has been that this wasn't explicitly clear, suggesting this change in wording to assist.
* Added feature-gates deprecation guidelines and policy as per discussion: SIG-architecture meeting
* Update deprecation-policy.md
Fixes and initial feedback incorporated.
* Removed unneeded sentence
Removed complicated sentence that is better phrased one sentence later.
* Incorporated feedback - Sept 22nd.
Re-structured following key ideas from the feedback.
* Fixed nits 7th October
Fixed nits 7th October
* Incorporated feedback Oct 25th
Incorporated 'invocation triggers warning' and what to do when disabling a no-op.
* fixed "tide"
Announced for completed
* Incorporated feedback from sig docs
* Update HAProxy ingress line
HAProxy Technologies offers support for the free available haproxy ingress controller
* Updated the haproxy wording from feedback
Updated the haproxy wording from feedback of @tengqm
* Remove doc artefacts
Will Beason