...

VMware VIO 4.0 Kubernetes Architecture

Image RemovedImage Added

Prerequisites

1. BlueShift Mgmt IP Address, username and password to create Kubernetes cluster .

2. K8S Master and K8S Node instances should have a OpenStack Flavor attached as per the requirement below

...

Steps to create a Kubernetes cluster

Follow the below steps 1 - 4

...

to create a Kubernetes cluster

Step 5 onwards are needed for getting the Kubernetes Host IP so that user can login to Kubernetes Host and ONAP using OOM can be deployed.

Step-1 - https://

...

MGMT_IP_ADDRESS/LOGIN

Step-2 Create the Cloud Provider before creating a kubernetes cluster 

...

Step-5  How to get Kubernetes Host host IP Address and login to Kubernetes Host  host  . 

5.1 - Login via console window  to  BLUESHIFT_MGMT_IP_ADDRESS . user name and password is same as used in step1 .

...

5.8 - Once inside KUBERNETES_HOST_IP_ADDRESS (to be reviewed)

Step-6  Installing kubectl to manage Kubernetes cluster  

  6.1 - Download the kubectl using below command 

...

sudo mv ./kubectl /usr/local/bin/kubectl 

Step-7 Verifying that kubectl config is good good
         

7.1 on - On Kubernetes Cluster  cluster  

        root@localhost:~# kubectl cluster-info

    Kubernetes master is

...

 7.2  on Client from where Kubernetes Cluster can be managed 

Step 8 Verifying that kubernetes config is good 

          8.1 on Kubernetes Cluster  

        root@localhost:~# kubectl cluster-info

Kubernetes master is running at https://10.110.208.207:443/
dnsmasq is running at https://10.110.208.207:443//api/v1/namespaces/kube-system/services/dnsmasq/proxy
kubedns is running at https://10.110.208.207:443//api/v1/namespaces/kube-system/services/kubedns/proxy

 8.2  on Client from where Kubernetes Cluster can be managed 

Step 9 Installing Helm 

...

 running at ....
    Heapster is running at....
    KubeDNS is running at ....
    kubernetes-dashboard is running at ...
    monitoring-grafana is running at ....
    monitoring-influxdb is running at ...
    tiller-deploy is running at....

7.2 - On client from Where Kubernetes cluster can be managed Remotely  

root@localhost:~# kubectl  version

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3",

Compiler:"gc", Platform:"linux/amd64"}

Server Version: version.Info{Major:"1", Minor:"7+", GitVersion:"v1.7.7-rancher1", GitCommit:"a1ea37c6f6d21f315a07631b17b9537881e1986a", GitTreeState:"clean", BuildDate:"2017-10-02T21:33:08Z",GoVersion:"go1.8.3" Compiler:"gc", Platform:"linux/amd64"}

Step-8 Verifying that kube config is good 

8.1 - On Kubernetes cluster  

root@localhost:~# cat  ~/.kube/config 

apiVersion: v1

kind: Config
clusters:
- cluster:
api-version: v1
insecure-skip-tls-verify: true
server: "<SERVER_IP_ADDRESS:8080/r/projects/CLUSTER_NAME/kubernetes:SERVER_PORT_NUMBER"
name: "(CLUSTER_NAME)"
contexts: 
- context:
cluster: "(CLUSTER_NAME)"
user: "(CLUSTER_NAME)"
name: "(CLUSTER_NAME)"
current-context: "(CLUSTER_NAME)"
users:
- name: "(CLUSTER_NAME/USER_NAME)"
user:
token: "<SECURITY_TOKEN>"

8.2 - On client from where Kubernetes cluster can be managed Remotely  

root@localhost:~# cat  ~/.kube/config 

current-context: default-context

apiVersion: v1
clusters:
- cluster:
api-version: v1
server: https://SERVER_IP_ADDRESS:SERVER_PORT_NUMBER/
insecure-skip-tls-verify: true
name: CLUSTER_NAME

contexts:
- context:
cluster: CLUSTER_NAME 
namespace: default
user: user1
name: default-context
users:
- name: user1
user:
username: "<USERNAME>"
password: "<PASSWORD"
kind: Config
preferences:
colors: true

Step-9 Installing Helm 

9.1 - Download the helm  using below command  

wget http://storage.googleapis.com/kubernetes-helm/helm-v2.3.0-linux-amd64.tar.gz

 99.2 - Download the helm  using below command  

...

sudo mv linux-amd64/helm /usr/local/bin/helm

Step-10 Verifying Helm  

 10.1  type 10.1 - Type the below command          helm

helm help

 10.2  helm 10.2 - Helm version .

              Client: &version.Version{SemVer:"v2.3.0", GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"}
              Server: &version.Version{SemVer:"v2.3.0", GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"}

...