Skip to content

Latest commit

 

History

History
87 lines (63 loc) · 3.35 KB

Hosting_Environments.md

File metadata and controls

87 lines (63 loc) · 3.35 KB
Raw

Hosting Environments

The Easy2Use environment can be deployed on your local laptop or any remote Docker host or Kubernetes cluster.

Local Laptop

Client Setup

Docker

Install Docker

Kubernetes

Kubectl

  • For manual administration of the Kubernetes cluster you could either use the Kubernetes Dashboard web GUI provided by your Kubernetes provider, or you could use the command line tool kubectl. Remember to set the environment variable KUBECONFIG to point to the config file for your Kubernetes cluster if you want to run kubectl commands towards your cluster.

    Install and Set Up kubectl

Helm/Tiller

  • To communicate with a Kubernetes cluster Easy2Use requires Helm to be installed on the client. After Helm is installed you should initialize the local helm CLI and install Tiller into your cluster by running 'helm init'.

    Install Helm

Remote Kubernetes Cluster

  • If you intend to deploy on a remote Kubernetes Cluster you don't need any additional client setup.

Kubernetes on Local Host (Windows with Hyper-V)

  • This is when you intend to run Kubernetes on your local host and also access it locally.

    ./easy2use configure-local-k8s-hyper-v

    Access Kubernetes dashboard via http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login

  • minikube on Local Host

    This is when you intend to run Kubernetes on your local host and also access it locally.

    ./easy2use configure-local-k8s-minikube

    Access Kubernetes dashboard

    minikube dashboard

  • Kubeconfig

    To run Easy2Use with Kubernetes a Kubeconfig file need to be provided by pointing out the specific Kubernetes cluster config file by setting KUBECONFIG environment variable.

    If bash shell is used, KUBECONFIG environment variable is set by following command:

    export KUBECONFIG=/path/to/admin.conf

    Kubernetes cluster kubeconfig file is often named admin.conf, but can be named to something else. The important thing is the KUBECONFIG variable points on correct kubeconfig file.

    If you have several Kubernetes Kubeconfig files, then you can switch between the Kubeconfig files by updating the KUBECONFIG variable with the path to the other kubeconfig file and then execute the Easy2Use command.

    export KUBECONFIG=/path/to/another.admin.conf