Welcome to Angry Admin channel. This channel is about my journey through an IT world. I started as probably most of you, from being help desk, phone help etc. I started as probably most of you, from being a help desk, phone help etc and now I am sysadmin. Very often I come across the issue where “uncle Google” cannot resolve it.
All the blogs and RU-vid videos are posting the same solution copied one from another but in fact the solution is not applicable to my environment.
Hence on my channel and blog you will find some of the issues quite unique as I am a lucky star for unexpected…
Enjoy! Please subscribe and share. Feedback are most welcome but keep it civil, please ;)
1. All updates, especially security ones impacting system stability should be ALWAYS rigorously tested before released to public. Company like CrowdStrike ranked for quite some time as no.2 world's security SW should basically guarantee that in the contract with their customers. Hiring or creating internal testing team rather than spending money elsewhere for example to pay executive bonuses is much better choice when sh*t hits the fan. 2. Companies should ALWAYS design their infrastructure with consideration to outages like this one by incorporating failover and redundancy features. Of course not everybody can afford complete redundancy for every machine they own, however basic redundancy and failover features is affordable for most of the companies out there. Overall I think it was good learning lesson especially for the big fat companies including CrowdStrike themselves to experience outage like this one. Hopefully they'll learn from them their mistakes and take necessary precautions to avoid them in the future. Either u r prepared or u r NOT!😎🤘
I think it all comes to robust DevOps practices and processes. The CEO of CrowdStrike was in the center of another major outage when he was a CTO for McAfee.
So... why do all these security software packages install themselves as drivers, and not just run ON TOP of the OS, instead of hooking into it at boot time?
Great👍 as always, waiting for new video series of VMWARE VMC Cloud and how to configure AWS and Azure in VMWARE VMC Cloud and new videos on VMWARE NSX Networking.
Hello, thanks for the video. But I see that everyone explains the same thing but it is not clear that the traffic with the NFS server is really going through the new virtual switch. IN my case I have three Virtual switches with VMKernels, Manage, the second for ISCSI and the third for NFS: Now in ISCSI I could select the switches, but in NFS I couldn't find a way to force the switch I want, since I manage a single network range. Any ideas? Thank you.
In an iSCSI setup, you can control which network switch is used by configuring the network settings on your initiators (clients) and targets (storage servers) to use specific IP addresses that are connected to the desired switches. This is often done through VLANs or dedicated physical interfaces that are connected to particular switches. NFS, on the other hand, is typically less granular in its network path control because it operates over IP networks and relies on the underlying network infrastructure and routing to determine the path taken.
@@PiotrTarnawski No, it cannot be replaced. Hopefully they will see sense and at the very least give a 90 free trial. There is greed and then there is stupidity.
@@AngryAdmin Looks like my issue was related to a cold snapshot of the vCSA. Deleted it, started the upgrade process again, and took a warm snap just before completing the process. Right sizes were available.
Amazing it is working now all nodes are Ready but how to expose the result I mean when you open the browser your master node IP or public DNS why I cannot reach the server if within the server I can execute command: "curl localhost" and I can see html welcome page from nginx. Basically I applied very simple kubernetes config for nginx Deployment + Service Load Balancer where "kubectl get svc" show me external ip of my loadbalancer service is pending (always pending) Deployment + Service ClusterIP + Ingress (Host public dns of master node) it is shown me nothing I could not reach the page And I have also tried port-forward command Maybe do you know to fix it? Thanks so much for your guide!
When I started watching the video I thought WOW I had exact same issue regarding :6443 Thanks man I will continue to watch this video and I hope everything will be fine. Btw I have tried to set up EKS and it was also failed for me I couldn't login from my local machine to kubernetes cluster... I was asked for some credentials but everything was set up with aws-cli. At the moment docker swarm looks better for me :)
I followed the same steps , also tried different installation methods but keep on receiving same error E: Unable to locate package kubelet E: Unable to locate package kubeadm E: Unable to locate package kubectl any idea about this error ?
Great to see you back Sir after long time, waiting to see thousands of new technical troubleshooting videos on VMWARE VSPHERE, VMWARE Cloud, VMWARE SDDC, AWS/AZURE in VMWARE CLOUD, NSX, VSAN, NSX-T video's soon.
Thank you! I have been struggling with this for too long only to realize I needed to add components already provided by VMware, but not automatically selected. I was able to export the image (json file) to use on multiple hosts/clusters.
Good monring I am having this issues where my self-signed certificate has expired but I am unable to logon to VCSA via SSH. Can this be done via the Grub shell.
Awesome great to see you back Sir with AWS, waiting for lots of new video's related to AWS on VMWARE VMC CLOUD and AWS configuration on VMWARE NSX/NSX-T and many more
Thanks for the video. It was very helpful. If we purchased keys, but lost track of them before we added them to vSphere, is there a specific place where we can find them?
Did you happen to forget the option "Import and replace certificate"? When where you going to explain how to replace an external CA certificate? You you tubers are all the same. All you care about is hearing yourself talk. You never check your work to make sure you explained what you set out to explain or if you actually did the work correctly and completely. Maybe you should stop and think about the folks who landed on your terrible video, the ones who don't have vmware support contracts in place and have very little time to replace their certificates before their whole infrastructure shuts down. You just wasted some of the precious time they have left to perform this ridiculously complicated process. There is one good thing about your video, you have now been admitted into the "Videos about important VMWare functions that so far no one(including the OEM) can explain step by step until completion" family of idiots.
Ignore the haters, haters are everywhere in every professions, you keep in making the best and most useful contents on VMWARE always as usual, wish to see lots of new technical troubleshooting contents and articles in the new year Related to VMWARE VSPHERE, VMWARE Cloud, NSX, VSAN, VMWARE Networking configuration for NSX and AWS environment, Happy new year to you and your family, stay safe and stay blessed always, God bless all
