aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com>2020-09-23 13:02:59 -0700
committerKuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com>2020-09-23 13:02:59 -0700
commite079d27a3ffd9a324ed61ceb1d9200c8a4ccfa7f (patch)
tree9b67aebb62705469cc6e15744bad1cc6b3d047d0
parent3b1566c55f5972b67a4aa729dddbaf9461825859 (diff)
fixing the README.md
Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: I3d3499862a472db76d801b9ee9ab520a4b521a15
-rw-r--r--README.md6
-rw-r--r--demo/sfc-setup/README.md14
2 files changed, 10 insertions, 10 deletions
diff --git a/README.md b/README.md
index 8fd91c6..365b232 100644
--- a/README.md
+++ b/README.md
@@ -61,6 +61,12 @@ In the master node run the `kubeadm init` as below. The ovn4nfv uses pod network
```
$ kubeadm init --kubernetes-version=1.19.0 --pod-network-cidr=10.233.64.0/18 --apiserver-advertise-address=<master_eth0_ip_address>
```
+Ensure the master node taint for no schedule is removed and labelled with `ovn4nfv-k8s-plugin=ovn-control-plane`
+```
+nodename=$(kubectl get node -o jsonpath='{.items[0].metadata.name}')
+kubectl taint node $nodename node-role.kubernetes.io/master:NoSchedule-
+kubectl label --overwrite node $nodename ovn4nfv-k8s-plugin=ovn-control-plane
+```
Deploy the ovn4nfv Pod network to the cluster.
```
$ kubectl apply -f deploy/ovn-daemonset.yaml
diff --git a/demo/sfc-setup/README.md b/demo/sfc-setup/README.md
index 676fa88..ef0dcc0 100644
--- a/demo/sfc-setup/README.md
+++ b/demo/sfc-setup/README.md
@@ -28,21 +28,15 @@ is available on the Vagrant site.
## Deployment
-### kubeadm
+### How to create K8s cluster?
Install the [docker](https://docs.docker.com/engine/install/ubuntu/) in the master, minion01 and minion02 vm.
Follow the steps in [create cluster kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) to create kubernetes cluster in master
-In the master vm run the `kubeadm init` as below. The ovn4nfv uses same pod network cidr `10.233.64.0/18`
-```
- $ kubeadm init --kubernetes-version=1.19.0 --pod-network-cidr=10.233.64.0/18 --apiserver-advertise-address=<master_eth0_ip_address>
-```
-Deploy the ovn4nfv Pod network to the cluster.
-```
- $ kubectl apply -f ovn4nfv-pod-network/ovn-daemonset.yaml
- $ kubectl apply -f ovn4nfv-pod-network/ovn4nfv-k8s-plugin.yaml
-```
+In the master vm run the `kubeadm init` as below. The ovn4nfv uses same pod network cidr `10.233.64.0/18`.
Join minion01 and minion02 by running the `kubeadm join` on each node as root as mentioned in [create cluster kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)
+Please follow the ovn4nfv installation steps - [ovn4nfv installation](https://github.com/ovn4nfv/ovn4nfv-k8s-plugin#quickstart-installation-guide)
+
### TM1 server
ssh into the TM1 vm and run the following command to attach TM1 to the left provider network.