Skip to content

Latest commit

 

History

History
 
 

Scenario-304

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
backup-storage.yaml
backup-storage.yaml
 
 
backup_db.sh
backup_db.sh
 
 
cronjob.yaml
cronjob.yaml
 
 
pv.yaml
pv.yaml
 
 
values.yaml
values.yaml
 
 

README.md

Table of Contents

Requirements

Scenario-304: Use helm To Deploy Service IV

  • Objective: Deploy elasticsearch cluster with 5 instances
  • Requirements:
1. Create an elasticsearch cluster
2. Scale the env to 5 instances

Background & Highlights

Procedures

Start k8s cluster

minikube start
eval $(minikube docker-env)

Install and run helm

https://github.com/kubernetes/charts/tree/master/stable/wordpress

https://deliciousbrains.com/running-wordpress-kubernetes-cluster

  • Start Helm
cd challenges-kubernetes/Scenario-304/
helm init
kubectl get pods --namespace kube-system
tiller_name=$(kubectl get pods --namespace kube-system | grep "tiller.*Running" | awk -F" " '{print $1}')
kubectl --namespace kube-system describe pod $tiller_name
helm repo update
# check whether the helm backend(tiller) is up and running
helm list
  • Run helm Deployment

values.yaml

helm install --name my-es -f values.yaml incubator/elasticsearch
  • Verify functionality after deployment
helm status my-es

Clean up

helm delete --purge my-es
minikube delete

More resources

https://github.com/kubernetes/charts/tree/master/incubator/elasticsearch
https://github.com/kubernetes/helm