To deploy a cluster in your AWS account with Kublr, you need to create an AWS policy and an AWS API Access Key. Please refer to Register AWS Policy, create User and Create API Credentials.
This document describes the steps necessary to show how Kublr works by creating a cluster in an Amazon Web Services infrastructure and deploying a simple application (WordPress). It contains the following steps:
Log into Kublr using your credentials.
On the left menu, click Credentials.
Click Add Credentials.
Set Credentials Type to “AWS Credentials”.
Enter Credentials Name.
Enter Access Key from AWS Management Console / IAM (see above).
Enter Secret Key from AWS Management Console / IAM (see above).
Select AWS partitions. You can select one of the following:
Note If you do not select any value, the “aws” standard partition is used.
Click Save Credentials. The “Credentials have been successfully created.” popup is displayed.
To verify if credentials are valid and ready to be used, mouse over the created credentials and click the displayed Test button.
Verification success popup is displayed.
Click Ok.
Powered by Kublr, Vanilla Kubernetes Cluster does not include any advanced Kublr features, suitable for running workloads.
To add a new cluster:
On the left menu, click Clusters.
Click Add Cluster.
The Select Intallation Type dialog is displayed.
In the Select Intallation Type dialog, click Cluster.
Click Continue Setup.
The ADD CLUSTER dialog is displayed.
In the ADD CLUSTER dialog, set Provider to “Amazon Web Services”.
From the Credentials list, select previosly created AWS credentials.
Specify Cluster Name.
Set:
Click the INSTANCES step.
Specify the parameters of the master node(s) of your cluster as described below.
Select Instance Type from the list.
From the Masters list, select the number of master or management nodes in correspondence with the selected Instance Type.
From the Operating System list, select the host OS for virtual machines in the cluster.
Optionally, select Public SSH Key from the list.
Scroll to the Instance Group section (default name group1).
Specify the parameters of the work node(s) in your group as described below.
Select Instance Type from the list.
To select the number of work nodes in a group, do one of the following:
From the Operating System list, select the host OS for virtual machines in the cluster.
If necessary, set your own name for the instance group.
Note You can also clone or delete the current instance group, or add another one.
Optionally, click the FEATURES step.
If necessary, add features to your cluster, specifying parameters under:
Click the REVIEW & CREATE step.
Review your cluster parameters.
At the bottom of the dialog, click CONFIRM AND INSTALL.
A notification is displayed “Your cluster is being created. It might take a few minutes.”
In the notification window, click OK.
Your new cluster page is displayed on the Events tab showing the cluster creation progress.
For more details, please refer to the official Kubernetes documentation
For Mac users:
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl
chmod +x ./kubectl
sudo mv ./kubectl /usr/local/bin/kubectl
For Windows users:
To retrieve the config from Kublr:
For Mac users:
mkdir ~/.kube
cp ~/Downloads/config.yaml ~/.kube/config
For Windows users:
cd %HOME%
mkdir .kube
copy %HOME%\Downloads\config.yaml .kube\config
Check that kubectl is working and using the correct config file:
kubectl config view
kubectl cluster-info
Install helm Click here for detailed guidelines.
For Mac users:
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh
chmod +x get_helm.sh
./get_helm.sh --version v2.9.1
For Windows users:
Initiate and test Helm installation:
helm init
NOTE: It may take a few minutes for the LoadBalancer IP to become available.
helm install stable/wordpress --name wordpress
For Mac users:
export SERVICE_IP=$(kubectl get svc --namespace default wordpress-wordpress -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
echo http://$SERVICE_IP/admin
echo Username: user
echo Password: $(kubectl get secret --namespace default wordpress-wordpress -o jsonpath='{.data.wordpress-password}' | base64 --decode)
Open the browser and navigate to the URL from console output.
For Windows users:
kubectl get svc --namespace default wordpress-wordpress -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'
kubectl get secret --namespace default wordpress-wordpress -o jsonpath='{.data.wordpress-password}