{"type":"doc","content":[{"type":"paragraph","content":[{"text":"This document provides instructions on how to setup HA Kubernetes cluster on AWS instances using Rancher Kubernetes Engine (RKE).","type":"text"}]},{"type":"paragraph","content":[{"text":"This document shows how to create and configure 3 control plane VMs (each with 4 vCPUs, 16GB RAM, 80GB disk storage & Ubuntu 18.04.4) and 12 worker VMs (each with 8 vCPUs, 32GB RAM, 160GB disk storage & Ubuntu 18.04.4) through AWS and deploy with HA kubernetes cluster through RKE.","type":"text"}]},{"type":"paragraph","content":[{"text":"Prerequisite: Users must have AWS account credentials to login and follow the below steps in AWS EC2/VPC dashboard.","type":"text"}]},{"type":"paragraph","content":[{"text":"1.Create Key Pair","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"A Key Pair is required to access the created AWS instances and will be used by RKE to configure the VMs for Kubernetes.","type":"text"}]},{"type":"paragraph","content":[{"text":"If key is already exists use an existing key pair and import through Import Key Pair","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Go to AWS EC2 dashboard click on Key Pairs in the left panel then click on Actions to Import","type":"text"}]}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"},{"type":"inlineExtension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"inline-media-image","parameters":{"width":"","id":"e9bb4171-ab57-4da8-b95e-a489e6b70d28","collection":"contentId-16454883","height":"250"}}}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"To Create New Key Pair:","type":"text"},{"type":"hardBreak"}]}]}]},{"type":"paragraph","content":[{"text":" Go to AWS EC2 dashboard click on Key Pairs in the left panel then click on Create Key Pair","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"},{"type":"inlineExtension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"inline-media-image","parameters":{"width":"","id":"806d1c76-fcb9-4eb1-8a54-bb5fc153c34a","collection":"contentId-16454883","height":"250"}}}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":" Note: Keep this downloaded key safe and copied into ~/.ssh/ from which it can be referenced. ","type":"text"}]},{"type":"codeBlock","content":[{"text":"Example:\n mv onap-key ~/.ssh\n chmod 600 ~/.ssh/onap-key\n\n\n","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"2.","type":"text"},{"text":"Create VPC","type":"text","marks":[{"type":"strong"}]},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"Go to AWS VPC dashboard click on Your VPCs in the left panel then click on Create VPC","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":54988,"__fileMimeType":"image/png","width":1343,"id":"09ee7455-824d-499c-b7d6-6027b02be0a1","collection":"contentId-16454883","type":"file","__fileName":"image18.png","height":543}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"3.","type":"text"},{"text":"Create Subnet","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Go to AWS VPC dashboard click on Subnets in the left panel then click on Create Subnet","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":53532,"__fileMimeType":"image/png","width":1347,"id":"11396a63-05cf-4b0e-9402-ab09406292ab","collection":"contentId-16454883","type":"file","__fileName":"image21.png","height":547}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"4.Create Internet Gateway","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Go to AWS VPC dashboard click on Internet Gateways in the left panel then click on Create Internet Gateway","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":86.0},"content":[{"type":"media","attrs":{"__fileSize":64826,"__fileMimeType":"image/png","width":1292,"id":"8ffe6c83-b41a-41cd-a510-79577de62a72","collection":"contentId-16454883","type":"file","__fileName":"image17.png","height":548}}]},{"type":"paragraph","content":[{"text":"Note: Once IGW is created, on the top right corner you will see Attach to VPC. Click on that button to attach this IGW to your VPC as below","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":88.0},"content":[{"type":"media","attrs":{"__fileSize":61067,"__fileMimeType":"image/png","width":1310,"id":"0445ef3c-7704-40e6-83dc-594f9191e72f","collection":"contentId-16454883","type":"file","__fileName":"image4.png","height":546}}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":4},"content":[{"text":"5.Add Routes with IGW","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Go to AWS VPC dashboard click on Route Tables in the left panel then select your routing table click on Routes and Edit Routes to Add route with IGW","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":45208,"__fileMimeType":"image/png","width":1341,"id":"f3714a74-f152-4a08-b012-2b2c1461aa55","collection":"contentId-16454883","type":"file","__fileName":"image20.png","height":543}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"6.Create Security Group","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Click on Create Security Group under EC2>Security Groups fill the details then click create security group","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":87.0},"content":[{"type":"media","attrs":{"__fileSize":54301,"__fileMimeType":"image/png","width":1291,"id":"1787bbe1-c5c6-44af-87f9-6f6fc0c068d5","collection":"contentId-16454883","type":"file","__fileName":"image5.png","height":540}}]},{"type":"paragraph","content":[{"text":"Select the created security group click on edit inbound & outbound rules ","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":87.0},"content":[{"type":"media","attrs":{"__fileSize":92374,"__fileMimeType":"image/png","width":1309,"id":"eb22ef60-504b-46b4-b169-d3d635ac6d83","collection":"contentId-16454883","type":"file","__fileName":"image6.png","height":548}}]},{"type":"paragraph","content":[{"text":"Add rules for Inbound:","type":"text"}]},{"type":"paragraph","content":[{"text":"Click on Add rule and fill the details then click on Save Rules","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":87.0},"content":[{"type":"media","attrs":{"__fileSize":55694,"__fileMimeType":"image/png","width":1296,"id":"0a9b02df-81d8-4376-8052-e95ef1ec1383","collection":"contentId-16454883","type":"file","__fileName":"image12.png","height":546}}]},{"type":"paragraph","content":[{"text":"Add Rules for Outbound:","type":"text"}]},{"type":"paragraph","content":[{"text":"Click on Edit Outbound rule and fill the details then click save rules","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":87.0},"content":[{"type":"media","attrs":{"__fileSize":59033,"__fileMimeType":"image/png","width":1307,"id":"faea6a63-5e14-405b-b45d-6595b1e95112","collection":"contentId-16454883","type":"file","__fileName":"image7.png","height":547}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"7.Create Kubernetes control plane VMs","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Step-1: Launch new instance from EC2 and select the image, click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":94.0},"content":[{"type":"media","attrs":{"__fileSize":68894,"__fileMimeType":"image/png","width":1341,"id":"b26f825e-a8f6-414e-a7bb-b08592afe425","collection":"contentId-16454883","type":"file","__fileName":"image13.png","height":519}}]},{"type":"paragraph","content":[{"text":"Step-2: Choose Instance Type, click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":89.0},"content":[{"type":"media","attrs":{"__fileSize":86373,"__fileMimeType":"image/png","width":1339,"id":"118eef1b-36e8-4497-aa34-1028eb90196c","collection":"contentId-16454883","type":"file","__fileName":"image16.png","height":550}}]},{"type":"paragraph","content":[{"text":"Step-3: Configure Instance","type":"text"}]},{"type":"paragraph","content":[{"text":"Select no of instances 3, network with your created VPC, subnet IDs & Enable Auto-assign Public IP then click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":92.0},"content":[{"type":"media","attrs":{"__fileSize":72661,"__fileMimeType":"image/png","width":1345,"id":"e5827739-a5e3-4ad0-8787-440a1f4ca17d","collection":"contentId-16454883","type":"file","__fileName":"image1.png","height":536}}]},{"type":"paragraph","content":[{"text":"Step-4: Add Storage:","type":"text"}]},{"type":"paragraph","content":[{"text":"Add disk storage as required then click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":77926,"__fileMimeType":"image/png","width":1343,"id":"1173aefe-444b-4655-af28-41a60bdbb67f","collection":"contentId-16454883","type":"file","__fileName":"image3.png","height":547}}]},{"type":"paragraph","content":[{"text":"Step-5: Add Tags","type":"text"}]},{"type":"paragraph","content":[{"text":"Add Tags if needed, click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":65108,"__fileMimeType":"image/png","width":1340,"id":"7ffa8c67-a70b-4b2d-9a13-ef0d7ecbf770","collection":"contentId-16454883","type":"file","__fileName":"image2.png","height":545}}]},{"type":"paragraph","content":[{"text":"Step-6: Configure Security Group","type":"text"}]},{"type":"paragraph","content":[{"text":"Create new security group or select existing security group if already exists then click on Review and Launch","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":89.0},"content":[{"type":"media","attrs":{"__fileSize":82716,"__fileMimeType":"image/png","width":1340,"id":"3f4795bf-3908-4fc5-a480-481840f4b447","collection":"contentId-16454883","type":"file","__fileName":"image23.png","height":551}}]},{"type":"paragraph","content":[{"text":"Step-7: Review and Launch","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":89.0},"content":[{"type":"media","attrs":{"__fileSize":62044,"__fileMimeType":"image/png","width":1340,"id":"e753fc1f-82cc-4612-8045-e4bc1155e6f4","collection":"contentId-16454883","type":"file","__fileName":"image11.png","height":548}}]},{"type":"paragraph","content":[{"text":"Note: While Launching select the Key Pair, check acknowledgement box and click Launch Instances","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":65.0},"content":[{"type":"media","attrs":{"__fileSize":181248,"__fileMimeType":"image/png","width":1366,"id":"32cc50c1-3d40-4cce-9fc6-96e7e369d255","collection":"contentId-16454883","type":"file","__fileName":"image22.png","height":768}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"8. Apply Customization script for control plane VMs","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Below is the Customization script, apply on all control plane VMs by running with “sudo ”","type":"text"}]},{"type":"codeBlock","content":[{"text":"#!/bin/bash\n\nDOCKER_VERSION=18.09.5\nsudo apt-get update\ncurl https://releases.rancher.com/install-docker/$DOCKER_VERSION.sh | sh\nsudo mkdir -p /etc/systemd/system/docker.service.d/\ncat > /etc/systemd/system/docker.service.d/docker.conf << EOF\n[Service]\nExecStart=\nExecStart=/usr/bin/dockerd -H fd:// --insecure-registry=nexus3.onap.org:10001\nEOF\nsudo usermod -aG docker ubuntu\nsudo systemctl daemon-reload\nsudo systemctl restart docker\nsudo apt-mark hold docker-ce\nIP_ADDR=`ip address |grep eth|grep inet|awk '{print $2}'| awk -F / '{print $1}'`\nHOSTNAME=`hostname`\necho \"$IP_ADDR $HOSTNAME\" >> /etc/hosts\nsudo docker login -u docker -p docker nexus3.onap.org:10001\nsudo apt-get install make -y\n\n#nfs server\nsudo apt-get install nfs-kernel-server -y\nsudo mkdir -p /nfs_share\nsudo chown nobody:nogroup /nfs_share/\nexit 0\n\n","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"9. Create Kubernetes Worker VMs","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"The number and size of Worker VMs is dependent on the size of the ONAP deployment. By default, all ONAP applications are deployed. It’s possible to customize the deployment and enable a subset of the ONAP applications. For the purpose of this guide, however, we will deploy 12 Kubernetes Workers that have been sized to handle the entire ONAP application workload.","type":"text"}]},{"type":"paragraph","content":[{"text":"Step-1: Launch new instance and select the required image","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"wide"},"content":[{"type":"media","attrs":{"__fileSize":62478,"__fileMimeType":"image/png","width":1335,"id":"bda16b2e-fd74-460d-8e2c-f87f2ca8269f","collection":"contentId-16454883","type":"file","__fileName":"image24.png","height":421}}]},{"type":"paragraph","content":[{"text":"Step-2: Choose an Instance Type","type":"text"}]},{"type":"paragraph","content":[{"text":"Select required configuration and click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":88399,"__fileMimeType":"image/png","width":1343,"id":"4f21fc46-95d0-4be5-b09d-a19df36b8b85","collection":"contentId-16454883","type":"file","__fileName":"image9.png","height":548}}]},{"type":"paragraph","content":[{"text":"Step-3: Configure Instances","type":"text"}]},{"type":"paragraph","content":[{"text":"Select no of instances, network and subnet details then click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":91.0},"content":[{"type":"media","attrs":{"__fileSize":76764,"__fileMimeType":"image/png","width":1345,"id":"ef134402-7d51-4486-ae7c-7879cc0bbb8a","collection":"contentId-16454883","type":"file","__fileName":"image26.png","height":542}}]},{"type":"paragraph","content":[{"text":"Step-4: Add Storage","type":"text"}]},{"type":"paragraph","content":[{"text":"Add required disk storage then click Next","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"wide"},"content":[{"type":"media","attrs":{"__fileSize":69484,"__fileMimeType":"image/png","width":1348,"id":"303ae7f0-cceb-4c01-9c98-230b6ac9d7b9","collection":"contentId-16454883","type":"file","__fileName":"image14.png","height":480}}]},{"type":"paragraph","content":[{"text":"Step-5: Add Tags","type":"text"}]},{"type":"paragraph","content":[{"text":"Select Add Tags if needed then click","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":65108,"__fileMimeType":"image/png","width":1340,"id":"7ffa8c67-a70b-4b2d-9a13-ef0d7ecbf770","collection":"contentId-16454883","type":"file","__fileName":"image2.png","height":545}}]},{"type":"paragraph","content":[{"text":"Step-6: Configure Security Group","type":"text"}]},{"type":"paragraph","content":[{"text":"Create new or Select existing security group then click Review and Launch","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":89.0},"content":[{"type":"media","attrs":{"__fileSize":82716,"__fileMimeType":"image/png","width":1340,"id":"3f4795bf-3908-4fc5-a480-481840f4b447","collection":"contentId-16454883","type":"file","__fileName":"image23.png","height":551}}]},{"type":"paragraph","content":[{"text":"Step-7: Review Instance Launch","type":"text"}]},{"type":"paragraph","content":[{"text":"Review the configuration details the click Launch","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":90.0},"content":[{"type":"media","attrs":{"__fileSize":64249,"__fileMimeType":"image/png","width":1343,"id":"f608eedd-5b59-45ad-b660-666300f8594f","collection":"contentId-16454883","type":"file","__fileName":"image15.png","height":544}}]},{"type":"paragraph","content":[{"text":"Note: While Launching select an existing key pair or create new, click acknowledgement checkbox then Launch","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":65.0},"content":[{"type":"media","attrs":{"__fileSize":181248,"__fileMimeType":"image/png","width":1366,"id":"32cc50c1-3d40-4cce-9fc6-96e7e369d255","collection":"contentId-16454883","type":"file","__fileName":"image22.png","height":768}}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"10. Apply Customization script for Kubernetes worker VMs","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Below is the Customization script, apply on all worker VMs by running with “sudo ”","type":"text"}]},{"type":"codeBlock","content":[{"text":"#!/bin/bash\n\nDOCKER_VERSION=18.09.5\nsudo apt-get update\ncurl https://releases.rancher.com/install-docker/$DOCKER_VERSION.sh | sh\nmkdir -p /etc/systemd/system/docker.service.d/\ncat > /etc/systemd/system/docker.service.d/docker.conf << EOF\n[Service]\nExecStart=\nExecStart=/usr/bin/dockerd -H fd:// --insecure-registry=nexus3.onap.org:10001\nEOF\nsudo usermod -aG docker ubuntu\nsystemctl daemon-reload\nsystemctl restart docker\napt-mark hold docker-ce\nIP_ADDR=`ip address |grep ens|grep inet|awk '{print $2}'| awk -F / '{print $1}'`\nHOSTNAME=`hostname`\necho \"$IP_ADDR $HOSTNAME\" >> /etc/hosts\ndocker login -u docker -p docker nexus3.onap.org:10001\nsudo apt-get install make -y\n# install nfs\nsudo apt-get install nfs-common -y\nexit 0\n\n","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"11. Configure Rancher Kubernetes Engine (RKE)","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"Download and install RKE on a VM, desktop or laptop. Binaries can be found here for Linux and Mac: ","type":"text"}]},{"type":"paragraph","content":[{"text":"https://github.com/rancher/rke/releases/tag/v1.0.6","type":"text","marks":[{"type":"link","attrs":{"href":"https://github.com/rancher/rke/releases/tag/v1.0.6"}}]}]},{"type":"paragraph","content":[{"text":"Execute below once RKE installed:","type":"text"}]},{"type":"codeBlock","content":[{"text":"mv rke_linux-amd64 rke\nsudo chmod +x rke\nsudo mv ./rke /usr/local/bin/rke\nrke -version\n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"RKE requires a cluster.yml as input. An example file is shown below that describes a Kubernetes cluster that will be mapped onto the AWS instances created earlier in this guide.","type":"text"}]},{"type":"paragraph","content":[{"text":"Below is an example of an HA Kubernetes cluster for ONAP","type":"text"}]},{"type":"codeBlock","content":[{"text":"nodes:\n- address: 172.31.47.230\n port: \"22\"\n internal_address: 172.31.47.230\n role:\n - controlplane\n - etcd\n hostname_override: \"onap-control-1\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.37.48\n port: \"22\"\n internal_address: 172.31.37.48\n role:\n - controlplane\n - etcd\n hostname_override: \"onap-control-2\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.35.44\n port: \"22\"\n internal_address: 172.31.35.44\n role:\n - controlplane\n - etcd\n hostname_override: \"onap-control-3\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.44.213\n port: \"22\"\n internal_address: 172.31.44.213\n role:\n - worker\n hostname_override: \"onap-wk-1\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.38.97\n port: \"22\"\n internal_address: 172.31.38.97\n role:\n - worker\n hostname_override: \"onap-wk-2\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.42.252\n port: \"22\"\n internal_address: 172.31.42.252\n role:\n - worker\n hostname_override: \"onap-wk-3\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.39.113\n port: \"22\"\n internal_address: 172.31.39.113\n role:\n - worker\n hostname_override: \"onap-wk-4\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.43.67\n port: \"22\"\n internal_address: 172.31.43.67\n role:\n - worker\n hostname_override: \"onap-wk-5\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.33.217\n port: \"22\"\n internal_address: 172.31.33.217\n role:\n - worker\n hostname_override: \"onap-wk-6\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.35.89\n port: \"22\"\n internal_address: 172.31.35.89\n role:\n - worker\n hostname_override: \"onap-wk-7\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.36.52\n port: \"22\"\n internal_address: 172.31.36.52\n role:\n - worker\n hostname_override: \"onap-wk-8\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.34.169\n port: \"22\"\n internal_address: 172.31.34.169\n role:\n - worker\n hostname_override: \"onap-wk-9\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.32.49\n port: \"22\"\n internal_address: 172.31.32.49\n role:\n - worker\n hostname_override: \"onap-wk-10\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.46.44\n port: \"22\"\n internal_address: 172.31.46.44\n role:\n - worker\n hostname_override: \"onap-wk-11\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\n- address: 172.31.47.93\n port: \"22\"\n internal_address: 172.31.47.93\n role:\n - worker\n hostname_override: \"onap-wk-12\"\n user: ubuntu\n ssh_key_path: \"~/.ssh/onap_key\"\nservices:\n kube-api:\n service_cluster_ip_range: 10.43.0.0/16\n pod_security_policy: false\n always_pull_images: false\n kube-controller:\n cluster_cidr: 10.42.0.0/16\n service_cluster_ip_range: 10.43.0.0/16\n kubelet:\n cluster_domain: cluster.local\n cluster_dns_server: 10.43.0.10\n fail_swap_on: false\nnetwork:\n plugin: canal\nauthentication:\n strategy: x509\nssh_key_path: \"~/.ssh/onap_key\"\nssh_agent_auth: false\nauthorization:\n mode: rbac\nignore_docker_version: false\nkubernetes_version: \"v1.15.11-rancher1-2\"\nprivate_registries:\n- url: nexus3.onap.org:10001\n user: docker\n password: docker\n is_default: true\ncluster_name: \"onap\"\nrestore:\n restore: false\n snapshot_name: \"\"\n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Prepare Cluster.yml ","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Before this configuration file can be used the external address and the internal_address must be mapped for each control and worker node in this file.","type":"text"}]},{"type":"paragraph","content":[{"text":"Run RKE:","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"From within the same directory as the cluster.yml file, simply execute:","type":"text"}]},{"type":"codeBlock","content":[{"text":"> rke up\nThe output will look something like this:\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.33.217]\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.47.230]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.33.217], try #1\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.47.230], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.39.113]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.39.113], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.43.67]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.43.67], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.35.89]\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.32.49]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.35.89], try #1\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.32.49], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.37.48]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.37.48], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.44.213]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.44.213], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.38.97]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.38.97], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.42.252]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.42.252], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.35.44]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.35.44], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.46.44]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.46.44], try #1\nINFO[0210] [cleanup] Successfully started [rke-log-cleaner] container on host [172.31.36.52]\nINFO[0210] Removing container [rke-log-cleaner] on host [172.31.36.52], try #1\nINFO[0210] [remove/rke-log-cleaner] Successfully removed container on host [172.31.47.230]\nINFO[0210] [remove/rke-log-cleaner] Successfully removed container on host [172.31.35.89]\nINFO[0210] [remove/rke-log-cleaner] Successfully removed container on host [172.31.34.169]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.32.49]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.35.44]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.39.113]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.33.217]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.43.67]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.37.48]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.42.252]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.38.97]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.46.44]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.36.52]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.44.213]\nINFO[0211] [remove/rke-log-cleaner] Successfully removed container on host [172.31.47.93]\nINFO[0211] [sync] Syncing nodes Labels and Taints\nINFO[0215] [sync] Successfully synced nodes Labels and Taints\nINFO[0215] [network] Setting up network plugin: canal\nINFO[0215] [addons] Saving ConfigMap for addon rke-network-plugin to Kubernetes\nINFO[0215] [addons] Successfully saved ConfigMap for addon rke-network-plugin to Kubernetes\nINFO[0215] [addons] Executing deploy job rke-network-plugin\nINFO[0220] [addons] Setting up coredns\nINFO[0220] [addons] Saving ConfigMap for addon rke-coredns-addon to Kubernetes\nINFO[0220] [addons] Successfully saved ConfigMap for addon rke-coredns-addon to Kubernetes\nINFO[0220] [addons] Executing deploy job rke-coredns-addon\nINFO[0225] [addons] CoreDNS deployed successfully..\nINFO[0225] [dns] DNS provider coredns deployed successfully\nINFO[0225] [addons] Setting up Metrics Server\nINFO[0225] [addons] Saving ConfigMap for addon rke-metrics-addon to Kubernetes\nINFO[0225] [addons] Successfully saved ConfigMap for addon rke-metrics-addon to Kubernetes\nINFO[0225] [addons] Executing deploy job rke-metrics-addon\nINFO[0230] [addons] Metrics Server deployed successfully\nINFO[0230] [ingress] Setting up nginx ingress controller\nINFO[0230] [addons] Saving ConfigMap for addon rke-ingress-controller to Kubernetes\nINFO[0230] [addons] Successfully saved ConfigMap for addon rke-ingress-controller to Kubernetes\nINFO[0230] [addons] Executing deploy job rke-ingress-controller\nINFO[0235] [ingress] ingress controller nginx deployed successfully\nINFO[0235] [addons] Setting up user addons\nINFO[0235] [addons] no user addons defined\nINFO[0235] Finished building Kubernetes cluster successfully\n\n","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"12. Install Kubectl and Validate K8S cluster Deployment","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Download and Install Kubectl. Binaries can be found here for Linux and Mac:","type":"text"}]},{"type":"paragraph","content":[{"text":"https://storage.googleapis.com/kubernetes-release/release/v1.15.11/bin/linux/amd64/kubectl","type":"text","marks":[{"type":"link","attrs":{"href":"https://storage.googleapis.com/kubernetes-release/release/v1.15.11/bin/linux/amd64/kubectl"}}]},{"type":"hardBreak"},{"text":"https://storage.googleapis.com/kubernetes-release/release/v1.15.11/bin/darwin/amd64/kubectl","type":"text","marks":[{"type":"link","attrs":{"href":"https://storage.googleapis.com/kubernetes-release/release/v1.15.11/bin/darwin/amd64/kubectl"}}]}]},{"type":"paragraph","content":[{"text":"Execute below after kubectl installation:","type":"text"}]},{"type":"codeBlock","content":[{"text":"chmod +x kubectl\nsudo mv kubectl /usr/local/bin/\nkubectl version --short --client\n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"To Validate K8S cluster deployment, execute below:","type":"text"}]},{"type":"codeBlock","content":[{"text":"mkdir -p ~/.kube\nsudo chown -R ubuntu kube_config_cluster.yml\ncp kube_config_cluster.yml ~/.kube/config.onap\nexport KUBECONFIG=~/.kube/config.onap\nkubectl config use-context onap\nkubectl get nodes -o=wide\n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Output will look something like this after successful Deployment:","type":"text"}]},{"type":"codeBlock","content":[{"text":"NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME\nonap-control-1 Ready controlplane,etcd 26d v1.15.11 172.31.47.230 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-control-2 Ready controlplane,etcd 26d v1.15.11 172.31.37.48 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-control-3 Ready controlplane,etcd 26d v1.15.11 172.31.35.44 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-1 Ready worker 26d v1.15.11 172.31.44.213 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-10 Ready worker 26d v1.15.11 172.31.32.49 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-11 Ready worker 26d v1.15.11 172.31.46.44 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-12 Ready worker 26d v1.15.11 172.31.47.93 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-2 Ready worker 26d v1.15.11 172.31.38.97 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-3 Ready worker 26d v1.15.11 172.31.42.252 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-4 Ready worker 26d v1.15.11 172.31.39.113 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-5 Ready worker 26d v1.15.11 172.31.43.67 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-6 Ready worker 26d v1.15.11 172.31.33.217 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-7 Ready worker 26d v1.15.11 172.31.35.89 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-8 Ready worker 26d v1.15.11 172.31.36.52 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\nonap-wk-9 Ready worker 26d v1.15.11 172.31.34.169 Ubuntu 18.04.4 LTS 5.3.0-1032-aws docker://18.9.5\n\n","type":"text"}]},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"},{"type":"paragraph"}],"version":1}

Browser not supported