Welcome to Seedha Logic - Your Gateway to DevOps & Data Science.
🚀 About Seedha Logic 🚀 Join us at Seedha Logic, an educational platform dedicated to empowering tech enthusiasts and developers with knowledge and skills in Cloud engineering and Data Science.
Cloud Engineering Skills: AWS, Kubernetes, DevOps, Data Skills: Python, SQL, BI Tool, Machine Learning, Deep Learning, Applied Artificial Intelligence.
Our mission is to demystify complex topics and provide practical insights to navigate the cloud computing landscape effortlessly.
Explore AWS Mastery, DevOps, and Kubernetes, and in Data Science we uncover fundamentals and advanced concepts.
Subscribe now, join our community, and embrace the power of AWS, Kubernetes, DevOps, and DataSciene. Let's shape a future of innovation and efficiency together!
Connect with us: Instagram - @seedhalogic Gmail - seedhalogic@gmail.com
Subnets is the networking area where your resources resides, a subnet having route through internet gw is public and subnet having route through NAT gw is private!
very great and simple explanation but I want to understa here one thing: in case of auto scaling groups it refers templates to know what ec2 instances to launch at the time of scaling. so, in case of karpenter how that works when karpenter provisioner scaled nodes and added one new node what reference it took for creation of ec2? @Seedha Logic
So when you create a karpenter provisioner you can define an instance types or families that karpenter will launch when it needs to scale out You can check this - karpenter.sh/v0.30/concepts/provisioners/
