Hi Alok, I am getting below error while installing. master01: E: Unable to locate package kubelet master01: E: Unable to locate package kubeadm master01: E: Unable to locate package kubectl The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.
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.
@skgiyasuddin8223 What are you doing that's having you use that network space and you not knowing subnetting? I hope this is a dev environment, becareful
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!
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.
thank you for your contribution! I got stuck on configure vm for kubernetes, getting a lot of errors about ports and joining worker nodes, you helped me a lot!
Thank you for this video But i have a problem, with i do all this steps and when i do kubectl get nodes doesn't work and i have error "kubectl command doesn't found"
Really good, works really well, I was avoiding creating k8s cluster on AWS or Azure and have been struggling to create a cluster on vagrant, very new to vagrant concept, was able to setup the master node, however the join command was throwing an error, then i came across your video, great work.
I have created a NodePort type service and i want to open it in browser but i need node ip. How can i get it? I run the command -> kubectl get nodes -o wide but it shows none external ip address
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"
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.
@@Priyanka-zg9gj Please let me know if you are finding it difficult to run the nodes at your end. Quick fix will be to check the versions of Virtualbox and Vagrant. should be updated. If specific error then please let me know here. I can try to fix and if required will upload updated version of this video. Thank you.
