วีดีโอ

Hello @skgiyasuddin8223, Can you please share the Address Space that you have set or want to set in your VNET? It can be 103.0.0.0/8 or 103.34.0.0/16 or 103.34.83.0/24 or something in between. it can only be confirmed with what is the Subnet Mask or CIDR we have set to Address Space.

Thank you sir

Hello @RachitaGupta-d2n, Thank you for trying out. Can you please provide more details on the error you are getting.

Hello @arunreddy1436 , Thank you for going through the video and asking question. You are absolutely right to say certificates that we have utilised to interconnect the Kubernetes core components and others will have a clear expiry date - usually 1-3 years (that we set during creation of cert) and it is part of SRE job that we need to renew the certificates before it expires. We use some automated tools like CERT MANAGER (cert-manager.io/docs/) which we have configured in our prod setup to automate the certificate renewal. I am looking forward to create a video on the same to provide better clarity. Hope this clarifies your question. Please let me know for any more queries. Thank you.

@@casa-cloud thank u so much for more insights, since u mentioned SRE role here, I’m curious to know what are the various other scenarios SRE will come into picture? It would be great help if u could share . I am sure that I won’t find such a clear answer.

Hello @arunreddy1436 the SRE work around Kubernetes is long but the key list is as followed 1. Certificate and Password Renewal 2. Incident Management - Network / Node failure 3. Compliance Auditing - real-time security monitoring and compliance. 4. Monitoring - Adding new and more smarter alerts for infra monitoring. Please share your thoughts on the same if you think should be in the list!

Thank you so much @satishkarengula9248 for your feedback, appreciate it :)

Thank you for the feedback @Nikhildeshmukh045 , appreciate it! :)

Hello, Really appreciate your feedback. Following are the response for your questions.. 1.do I need to have configured Virtual Box - NO NEED. by default vagrant will search for Virtual Box 2.VM before using vagrant up command - NO, vagrant will pull the latest vagrant box - ubuntu/bionic64 which I have configured in github.com/ImaginCloud/kubernetes/blob/main/setup-k8s/theHardWay/Vagrantfile Line 13. All the required configuration are by default given the Vagrant Box - ubuntu/bionic64. Let me know if need any more information. Thank you.

hello, the IP's to the nodes are given from the Vagrant script - github.com/ImaginCloud/kubernetes/blob/main/setup-k8s/vagrant-kubeadm/Vagrantfile IP_NW = "192.168.56." MASTER_IP_START = 1 NODE_IP_START = 2 And the loop for master VM's is Line 25 - node.vm.network :private_network, ip: IP_NW + "#{MASTER_IP_START + i}" And the loop for Worker VM's is Line 44 - node.vm.network :private_network, ip: IP_NW + "#{NODE_IP_START + i}" Please let me know if you need any more details

By default you do not need a password as VM is initiated by Vagrant, but if the vagrant configurations are not set to its default then you can use password "vagrant". please let me know if you are finding any other error. I will try to solve it.