May02 Kubernates Class

SRINI VASAN5:17 PM
Oh sorry done
Badri R5:25 PM
yes
vamsi krishna5:25 PM
yes
Kalaiarasan Kirubanandam5:25 PM
I have a few doubts
sathyaraj k5:25 PM
yes
can we attach the roles to user group(s)?
can we attach the role(s) to user(s)?
can we attach the k8s objects assigned to roles - roles assigned to group and group
assinged to networkgroup?
Badri R5:30 PM
clear.
Thulasiraja m6:10 PM
Yes
s
Saju Krishnan6:10 PM
yes
vaithiy anathan6:10 PM
yes
Mani kandan6:32 PM
looks like my vm got corrupted need to check on john
$ script/vagrant/sloopstash-k8s-mtr/up
Vagrant failed to initialize at a very early stage:
The machine index which stores all required information about

running Vagrant environments has become corrupt. This is usually
caused by external tampering of the Vagrant data folder.
Vagrant cannot manage any Vagrant environments if the index is

corrupt. Please attempt to manually correct it. If you are unable
to manually correct it, then remove the data file at the path below.
This will leave all exist
yes
archana sekar6:36 PM
yes
Tajdeen Abdulla6:36 PM
Yes
sathyaraj k6:36 PM
Yes
Jaicy Vignesh6:36 PM
s
harvind kumar6:36 PM
yes
Sathishkumar M6:36 PM
es
somasundaram selvamuthukumar6:36 PM
yeas
Aanchal Mathew6:36 PM
yes
Kolli Santhosh6:36 PM
yes
Sathiyaraj Sridhar6:40 PM
vim ~/.kube/config
cd /opt/kickstart-kubernetes
kubectl apply -f role/devops.yml -n crm-stg
kubectl apply -f role/developer.yml -n crm-stg
kubectl apply -f role/qa.yml -n crm-stg
kubectl get roles -o wide --show-labels=true -n crm-stg
Vishal S6:45 PM
s
sathyaraj k6:45 PM
Yes
Arunkumar Ponnurangam6:45 PM
yes
yes
yes
BANDITA GARNAIK6:46 PM
yes
done
s
John Sundarraj6:47 PM
Windows host machine users open new Git Bash terminal
Ubuntu host machine users open new terminal.
Rajkumar R T6:48 PM
yes
yes
sathyaraj k6:48 PM
Yes
Rajkumar R T6:48 PM
vim ~/.kube/config
able to see
s
Azharudeen AshrafAli6:49 PM
k
Vishal S6:49 PM
s
yes
kubectl get pods -o wide --show-labels=true -n crm-stg
yes
yes
yes
S
yes
Vishal S6:51 PM
s
Rajkumar R T6:51 PM
bash: kubectl: command not found
kubectl apply -f role/qa.yml -n crm-stg
kubectl get rolebindings -o wide --show-labels=true -n crm-stg
yes
yes
Yes
yes
yes
yes
kubectl get services -o wide --show-labels=true -n crm-stg
kubectl delete -f service/app.yml -n crm-stg
yes
yes
Yes
kubectl apply -f role/binding/devops.yml -n crm-stg
yes
Kavi Arasu6:59 PM
yes
yes
s
yes
yes
kubectl delete -f role/binding/devops.yml -n crm-stg
Will be back in 10 mins after break.
Mani kandan7:18 PM
Sudharshan_Pranav@DESKTOP-V1GLSSN MINGW64 /opt/kickstart-kubernetes (master)
$ script/vagrant/sloopstash-k8s-mtr/destroy
Vagrant failed to initialize at a very early stage:
The machine index which stores all required information about

running Vagrant environments has become corrupt. This is usually
caused by external tampering of the Vagrant data folder.
Vagrant cannot manage any Vagrant environments if the index is

corrupt. Please attempt to manually correct it. If you are unable
to manually
@Manikandan: just deleted the index file and the .lock file from the machine-index
folder
@Manikandan: And then up the VM.
kubectl get nodes -o wide --show-labels=false
kubectl apply -f cluster-role/qa.yml
kubectl get clusterroles -o wide --show-labels=true
kubectl apply -f cluster-role/binding/qa.yml
kubectl get clusterrolebindings -o wide --show-labels=true
yes
yes
yes
yes
Yes
s
karthik s7:47 PM
Working
yes
yes
sathyaraj k7:48 PM
Yes
Vishal S7:48 PM
s
kubectl drain sloopstash-k8s-wkr --delete-local-data --force --ignore-daemonsets
kubectl apply -f cluster-role/devops.yml
kubectl get clusterroles -o wide --show-labels=true | grep devops
kubectl apply -f cluster-role/binding/devops.yml
sathyaraj k7:55 PM
yes
yes John
s
Shivakanth Chandrasekaran7:55 PM
s
yes
sudo docker container ls
kubectl drain sloopstash-k8s-mtr --delete-local-data --force --ignore-daemonsets
do we also need to delete the worker node...?
yes
sathyaraj k8:03 PM
yes
in real time, when we will use for drain?
yes
Kavi Arasu8:03 PM
yes
yes
yes
yes
Swati Anpat8:03 PM
yes
journalctl -f -u kubelet.service
tq
kubectl delete node sloopstash-k8s-wkr
yes
ganesh8:07 PM
yes
Rajkumar R T8:07 PM
s
s
yes
sudo kubeadm reset
sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo
iptables -X
kubectl delete node sloopstash-k8s-mtr
sudo docker container ls
sudo kubeadm reset
sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo
iptables -X
Rajkumar R T8:14 PM
yes
done
yes
sudha TM8:14 PM
yes
Kavi Arasu8:14 PM
yes
yes
s
Vishal S8:14 PM
s
ganesh8:14 PM
yes
sathyaraj k8:14 PM
Yes
yes
Azharudeen AshrafAli8:26 PM
These topics when we are planned to cover>> kubectl rollout
>> node affinity
>> stateful set - for db service
thanks John.. Recall the Docker,Swarm and K8S
Muthu Kumaran8:51 PM
Also aoutoscaling conepts and renewing certificate and daemon sets
These are some common interview questions
Kubes.aws8:59 PM
Thanks John and Satyaraj!

May02 Kubernates Class

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

May02 Kubernates Class

Uploaded by

Copyright:

Available Formats

SRINI VASAN5:17 PM

The machine index which stores all required information about

Vagrant cannot manage any Vagrant environments if the index is

The machine index which stores all required information about

Vagrant cannot manage any Vagrant environments if the index is

You might also like