
az group create --name dev-rg --location West US 3
az aks create \
--resource-group prod-rg \
--name aks-dev-eu-01 \
--kubernetes-version 1.23.12 \
--enable-private-cluster \
--network-plugin azure \
--node-count 2 \
--node-vm-size standard_d11_v2_promo \
--nodepool-name aksdeveu01 \
--zones 1 2 \
--enable-aad \
--enable-managed-identity \
--vnet-subnet-id /subscriptions/46acd488-1ecb-40b4-9980-e2baff0fc33c/resourceGroups/prod-rg/providers/Microsoft.Network/virtualNetworks/PROD-VNET-WU-01/subnets/prod-subnet \
--docker-bridge-address 172.17.0.1/16 \
--dns-service-ip 10.0.0.10 \
--service-cidr 10.0.0.0/24 \
--tags "env=dev" \
--generate-ssh-keys
kubectl describe nodes | grep -e "Name:" -e "failure-domain.beta.kubernetes.io/zone"
apiVersion: v1
kind: PersistentVolume
metadata:
name: new-pvc
spec:
capacity:
storage: 1Gi
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Retain
storageClassName: storageclass
csi:
driver: disk.csi.azure.com
readOnly: false
volumeHandle: /subscriptions/46acd488-1ecb-40b4-9980-e2baff0fc33c/resourcegroups/MC_dev-rg_aks-dev-we-01_westus3/providers/Microsoft.Compute/disks/disk-zone-02
volumeAttributes:
fsType: ext4
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: storage-new-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
volumeName: new-pvc
storageClassName: storageclass
allowVolumeExpansion: false
allowedTopologies:
- matchLabelExpressions:
- key: failure-domain.beta.kubernetes.io/zone
values:
- westus3-1
- westus3-2
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
labels:
kubernetes.io/cluster-service: "true"
name: storageclass
parameters:
kind: Managed
storageaccounttype: Standard_LRS
provisioner: kubernetes.io/azure-disk
reclaimPolicy: Retain
volumeBindingMode: WaitForFirstConsumer
=-
# kubectl label nodes <node-name> <label-key>=<label-value>
# kubectl label nodes node-01 disktype=ssd
# kubectl get nodes node-01 --show-labels (to verify the attached labels)
In this session, i have mainly focused on all use cases in Kubernetes project like which type of client requirement or customer requirement in Kubernetes environment. So that you will get real time exposure in Kubernetes and have idea about customer requirement in Kubernetes
In This Session I have Covered Used Case or scenario based Requirement Given By Customer or Client In Kubernetes Production Environment. I Have Created All Used Case which I faced in my Entire Kubernetes Journey.
Based on That i have created so that other one have better Understanding about Day to Day task in Kubernetes Environment and Which type of Requirement is given by Customer in Kubernetes ENV.
Most of the interviewer asked you to tell me about challenges which you were working on in your Kubernetes project.
After watching my session that would be more helpful. I have covered all the Topics which are based on the real time environment, which generally I worked and have faced those issues in my Kubernetes project.
This session will be helpful for those folks who have good knowledge about Kubernetes but don't have a chance to get a job in Kubernetes or no knowledge about real time scenarios in industry, due to the lack of this thing they are not confident during the interview. I will explain about Kubernetes infrastructure like all tools we have used in industry, and also share a list of interview questions.
Nowadays most of the companies have adopted containerization based applications and deploy applications over Kubernetes Platform so there are a lot of opportunities only on Kubernetes profile itself. Most guys have confusion that only devops openings are there but it's not true...Generally devops guys set up CICD Pipeline or Set Release pipeline over kubernetes environment. So company needs seperate team to manage entire kubernetes infrastructure, Generally in project 100+ kubernetes cluster 400+ application running as a pod so we need seperate team to manage entire infrastructure and we have to upgrade cluster time to time also