From e079d27a3ffd9a324ed61ceb1d9200c8a4ccfa7f Mon Sep 17 00:00:00 2001 From: Kuralamudhan Ramakrishnan Date: Wed, 23 Sep 2020 13:02:59 -0700 Subject: fixing the README.md Signed-off-by: Kuralamudhan Ramakrishnan Change-Id: I3d3499862a472db76d801b9ee9ab520a4b521a15 --- demo/sfc-setup/README.md | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) (limited to 'demo') 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= -``` -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. -- cgit 1.2.3-korg