Signed-off-by: yanan Lee <energylyn@zju.edu.cn>
Incorrect spelling
Signed-off-by: yanan Lee <energylyn@zju.edu.cn>
spelling error
Signed-off-by: yanan Lee <energylyn@zju.edu.cn>
Incorrect spelling
Signed-off-by: yanan Lee <energylyn@zju.edu.cn>
Revert "Incorrect spelling"
fix some typos
Signed-off-by: Jie Luo <luo612@zju.edu.cn>
fix a typo
Signed-off-by: Jie Luo <luo612@zju.edu.cn>
fix a typo
Signed-off-by: Jie Luo <luo612@zju.edu.cn>
Provide valid --cloud-providers, vagrant and openshift were listed but is not actually a valid cloud provider in this context in the current code base while a number of other valid options were omitted including azure, cloudstack, openstack, photon and vsphere.
The original one is: "kops update cluster useast1.dev.awsdata.com --yes"
However, the previous example used useast1.dev.example.com to create configuration file.
So, the "awsdata" should be changed into example.
Although the Fedora install docs are under the "Bare Metal"
section in the docs, the instructions provided work fine
for Fedora installs in virtual machines
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The Fedora multi-node doc need to tell users to install
flannel, since previous setup won't have brought it in.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The install of kubernetes pulls in docker, which has a direct
dependancy on iptables. So there is no need to tell people to
yum install iptables manually.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The /var/run/kubernetes directory is already created by
installation of the kubernetes RPM with correct user
and group ownership and permissions.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The docs still refer to etcd using port 4001, but in all
currently released Fedora versions it will be using 2379
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>