Anwesha Rath

One essential 𝐒3 𝐋𝐢𝐟𝐞𝐜𝐲𝐜𝐥𝐞 configuration that you must have for 𝐞𝐯𝐞𝐫𝐲 𝐒3 𝐛𝐮𝐜𝐤𝐞𝐭 is to delete incomplete multipart uploads. A few things to know about multipart uploads: 👉 By default, based on the file size you're uploading, AWS SDKs and tools will automatically choose multipart upload, like the 𝘢𝘸𝘴 𝘴3 𝘤𝘱 command. 👉 If the complete multipart upload request isn’t successfully sent, Amazon S3 will not assemble the parts, and the object will not be created. However, the incomplete parts will remain in your Amazon S3 bucket. 👉 You will continue to be charged for incomplete or discarded multipart uploads, regardless of the storage class. For S3 Glacier or S3 Glacier Deep Archive, you will also be charged for staging storage used for in-progress multipart uploads. The best way to manage this is by 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐢𝐧𝐠 𝐚𝐧 𝐒3 𝐥𝐢𝐟𝐞𝐜𝐲𝐜𝐥𝐞 𝐩𝐨𝐥𝐢𝐜𝐲 to automatically clean up incomplete uploads. #aws #s3 #devops #bucket #hackwithharsha #python #cloud #java #go

𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗢𝗽𝗲𝗻 𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝘀 (𝗢𝗖𝗜, 𝗖𝗥𝗜, 𝗖𝗡𝗜, 𝗖𝗦𝗜, 𝗦𝗠𝗜, 𝗖𝗜𝗟) Kubernetes, the de facto standard for container orchestration, relies on a robust ecosystem of open standards. These standards are developed and maintained by the community and define how different components interact within the system 𝗞𝗲𝘆 𝗯𝗲𝗻𝗲𝗳𝗶𝘁𝘀 🔶 𝙄𝙣𝙩𝙚𝙧𝙤𝙥𝙚𝙧𝙖𝙗𝙞𝙡𝙞𝙩𝙮: Different vendors can create products adhering to the same standard, ensuring seamless integration. 🔶 𝙁𝙡𝙚𝙭𝙞𝙗𝙞𝙡𝙞𝙩𝙮: You can choose components and plugins from various vendors based on your specific needs. 𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝘀 : 🔶 𝙊𝙥𝙚𝙣 𝘾𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙄𝙣𝙞𝙩𝙞𝙖𝙩𝙞𝙫𝙚 (𝙊𝘾𝙄): Defines a standard for container image formats and runtimes. Popular examples include 𝘋𝘰𝘤𝘬𝘦𝘳, 𝘊𝘙𝘐-𝘖, 𝘢𝘯𝘥 𝘙𝘒𝘛 images. 🔶 𝘾𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙍𝙪𝙣𝙩𝙞𝙢𝙚 𝙄𝙣𝙩𝙚𝙧𝙛𝙖𝙘𝙚 (𝘾𝙍𝙄): Establishes a consistent way for Kubernetes to interact with different container runtimes. CRI utilizes a plugin architecture, allowing support for various Runtime options like 𝘊𝘙𝘐-𝘖, c𝘰𝘯𝘵𝘢𝘪𝘯𝘦𝘳𝘥 etc 🔶 𝘾𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙉𝙚𝙩𝙬𝙤𝙧𝙠 𝙄𝙣𝙩𝙚𝙧𝙛𝙖𝙘𝙚 (𝘾𝙉𝙄): Provides a specification and toolset for configuring network interfaces within containers. This plugin architecture enables Kubernetes to integrate with various network plugins like 𝘍𝘭𝘢𝘯𝘯𝘦𝘭, 𝘊𝘢𝘭𝘪𝘤𝘰, 𝘢𝘯𝘥 𝘞𝘦𝘢𝘷𝘦 𝘕𝘦𝘵. 🔶 𝘾𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙎𝙩𝙤𝙧𝙖𝙜𝙚 𝙄𝙣𝙩𝙚𝙧𝙛𝙖𝙘𝙚 (𝘾𝙎𝙄): Facilitates communication between Kubernetes and diverse storage providers. Storage providers can develop CSI plugins that are compatible with various container orchestration systems. Examples 𝘈𝘞𝘚 𝘌𝘭𝘢𝘴𝘵𝘪𝘤 𝘉𝘭𝘰𝘤𝘬 𝘚𝘵𝘰𝘳𝘢𝘨𝘦, 𝘕𝘦𝘵𝘈𝘱𝘱 etc. 🔶 𝙎𝙚𝙧𝙫𝙞𝙘𝙚 𝙈𝙚𝙨𝙝 𝙄𝙣𝙩𝙚𝙧𝙛𝙖𝙘𝙚 (𝙎𝙈𝙄): Defines a standard for service meshes on Kubernetes, allowing consistent interaction with different service mesh implementations like 𝘐𝘴𝘵𝘪𝘰, 𝘓𝘪𝘯𝘬𝘦𝘳𝘥 etc 🔶 𝘾𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙄𝙢𝙖𝙜𝙚 𝙇𝙞𝙗𝙧𝙖𝙧𝙮 (𝘾𝙄𝙇): This set of specifications defines how container images are stored, indexed, and distributed. Major container registries like 𝘋𝘰𝘤𝘬𝘦𝘳 𝘏𝘶𝘣, 𝘘𝘶𝘢𝘺.𝘪𝘰, 𝘢𝘯𝘥 𝘏𝘢𝘳𝘣𝘰𝘳 leverage CIL for sharing and reusing container images across various platforms and environments. #kubernetes #Containerization #Cloud

8

How Mandar Sarfare received 400% hike in DevOps with 90 days notice period https://lnkd.in/g6GBv5Fb There are times when we have a fear on how to tackle the 90 Days notice period or how we have to approach someone to get a job or it might be funny sometimes to put papers without any job in current organisation. But yes we have Mandar with us in this video who reveals all his story about the placement being the BCA graduate background.  In this video he explained about 1) 90 Days notice period tackle 2)Job search portals that helped him 3) Linkedin hacks that he used 4) Finally the BSC graduate becoming DevOps engineer journey Note - This video was recorded along with the Part1 , so if you have missed the part1 it is here https://lnkd.in/gqsQRuTZ If you have read the post till here, do share with your BSC graduate friends :)

314

10 Comments

𝑲𝒖𝒃𝒆𝒓𝒏𝒆𝒕𝒆𝒔 𝒓𝒐𝒂𝒅𝒎𝒂𝒑 𝐂𝐨𝐫𝐞 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬: Understand the fundamentals of Kubernetes including clusters, services, deployments, and replicasets. 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐂𝐨𝐧𝐭𝐫𝐨𝐥 𝐏𝐥𝐚𝐧𝐞: Dive into the architecture with nodes, operators, control planes, and key components like etcd and Kubelet. 𝐀𝐮𝐭𝐨 𝐒𝐜𝐚𝐥𝐢𝐧𝐠 & 𝐋𝐨𝐚𝐝 𝐁𝐚𝐥𝐚𝐧𝐜𝐢𝐧𝐠: Explore scaling options with horizontal and vertical autoscalers, load balancers, and cluster autoscaling. 𝐒𝐭𝐚𝐭𝐞𝐟𝐮𝐥 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 & 𝐃𝐚𝐭𝐚 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Learn about managing stateful applications, persistent volumes, custom resource definitions, and data handling with CSI. 𝐏𝐚𝐜𝐤𝐚𝐠𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 & 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧: Utilize tools like Helm, Kustomize, and Operators Framework for package management and configuration. 𝐁𝐚𝐜𝐤𝐮𝐩, 𝐑𝐞𝐬𝐭𝐨𝐫𝐞, 𝐚𝐧𝐝 𝐃𝐢𝐬𝐚𝐬𝐭𝐞𝐫 𝐑𝐞𝐜𝐨𝐯𝐞𝐫𝐲: Ensure data integrity with backup, restore, and disaster recovery strategies. 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 & 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭: Implement CI/CD practices with GitOps, canary and blue-green deployments, and rolling updates. 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐚𝐧𝐝 𝐈𝐝𝐞𝐧𝐭𝐢𝐭𝐲 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Secure your Kubernetes environment with RBAC, IAM, encryption, firewalls, and access controls. 𝐍𝐞𝐭𝐰𝐨𝐫𝐤𝐢𝐧𝐠: Manage networking aspects with DNS, CNI, Kubeproxy, and network policies. 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐚𝐧𝐝 𝐎𝐛𝐬𝐞𝐫𝐯𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Monitor and track metrics, events, and logs with tools like Prometheus, Grafana, and OpenTelemetry. 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 ->https://app.thealpha.dev/ post Credit -: Paras Mayur

26

2 Comments

💡 Use 𝐫𝐞𝐜𝐮𝐫𝐬𝐢𝐯𝐞 flag along with 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐞𝐱𝐩𝐥𝐚𝐢𝐧 command to get all the fields available for that Kubernetes resource. Following is the example command for deployment resource. >>> 𝘬𝘶𝘣𝘦𝘤𝘵𝘭 𝘦𝘹𝘱𝘭𝘢𝘪𝘯 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵 --𝘳𝘦𝘤𝘶𝘳𝘴𝘪𝘷𝘦 and then, If you want to deep dive into any of the field, use following command along with field name. In this scenario, I am looking for 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵.𝘴𝘱𝘦𝘤.𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 >>> 𝘬𝘶𝘣𝘦𝘤𝘵𝘭 𝘦𝘹𝘱𝘭𝘢𝘪𝘯 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵.𝘴𝘱𝘦𝘤.𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 #kubernetes #devops #docker #sre #hackwithharsha #python #java

3

1 Comment

𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐏𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 The DevOps/SRE engineer always are responsible to handle the production issues and to save your from any escalation this post is curated: 𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 : A single-machine Kubernetes learning environment has a single point of failure. Creating a highly available cluster means considering: - Separating the control plane from the worker nodes. - Replicating the control plane components on multiple nodes. - Load balancing traffic to the cluster’s API server. - Having enough worker nodes available, or able to quickly become available, as changing workloads warrant it. 𝐒𝐜𝐚𝐥𝐞 : If you expect your production Kubernetes environment to receive a stable amount of demand, you might be able to set up for the capacity you need and be done. However, if you expect demand to grow over time or change dramatically based on things like season or special events, you need to plan how to scale to relieve increased pressure from more requests to the control plane and worker nodes or scale down to reduce unused resources. 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐚𝐧𝐝 𝐚𝐜𝐜𝐞𝐬𝐬 𝐦𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 : You have full admin privileges on your own Kubernetes learning cluster. But shared clusters with important workloads, and more than one or two users, require a more refined approach to who and what can access cluster resources. You can use role-based access control (RBAC) and other security mechanisms to make sure that users and workloads can get access to the resources they need, while keeping workloads, and the cluster itself, secure. You can set limits on the resources that users and workloads can access by managing policies and container resources. If you need any help on your job search then join do checkout the prime batch8 exclusive on DevOps/SRE content 𝐖𝐡𝐲 𝐭𝐡𝐢𝐬 𝐃𝐞𝐯𝐎𝐩𝐬 𝐂𝐨𝐮𝐫𝐬𝐞 by Praveen Singampalli ?? 📌Easy to learn with 14 projects 📌The best in DevOps tools included for 2024 📌Mock interviews/resume reviews/doubts session 📌Live Classes/recorded sessions 📌Each session backed by a project 📌Roles and responsibilities document for each project 📌 More details check here https://lnkd.in/gF2fs6jF 𝐄𝐧𝐫𝐨𝐥𝐥 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐜𝐨𝐮𝐫𝐬𝐞 : https://lnkd.in/gF2fs6jF [Classes starting in 1 week] 

280

9 Comments

🌟 Day 91 of #100DaysOfLeetCode Challenge! 🚀 Today I solved the problem no. 50 on LeetCode: Pow(x, n) APPROACH : 1. If n == 0: Any number raised to the power of 0 is 1, so return 1. 2. If x == 0: Any non-zero number raised to the power of 0 is 1, so return 0. 3. If n < 0: We need to compute the reciprocal of x raised to the positive value of n (-n). This is handled by setting x = 1/x and making n positive (n = -n). 4. Initialize ans to 1, which will accumulate the result of x raised to the power as we iterate. 5. Use a while loop that continues as long as n is non-zero. 6. Inside the loop: If n is even (n % 2 == 0), square x (x = x * x) and halve n (n = n / 2). If n is odd (n % 2 == 1), multiply ans by x (ans = ans * x) and decrement n by 1 (n = n - 1). 7. Once the while loop completes (i.e., n becomes zero), ans contains x raised to the power of n, considering the adjustments made for negative exponents (if any). 8. Return ans, which is the computed result of x raised to the power n. TIME COMPLEXITY: O(logn) SPACE COMPLEXITY: O(1) Feel free to contribute your approaches as well. #100DaysOfLeetCode #CodingChallenge #Algorithms #Programming  #TechSkills #CodingAdventure #GeekModeActivated  #leetcodechallenge

14

Day 6 of learning about Kubernetes: 𝐊𝐞𝐲𝐰𝐨𝐫𝐝𝐬 𝐢𝐧 𝐏𝐨𝐝 𝐌𝐚𝐧𝐢𝐟𝐞𝐬𝐭𝐬 𝐚𝐩𝐢𝐕𝐞𝐫𝐬𝐢𝐨𝐧 => Version of Kubernetes API (For compatibility between cluster and manifests file) 𝐦𝐞𝐭𝐚𝐝𝐚𝐭𝐚 => Labels (Key-value pairs) attached to the pods 𝐬𝐩𝐞𝐜 => Container Specifications like name, image, exposed port etc. #kubernetes #learning #day6 #dailyseries #pods #podmanifests #labels #devops

9

1 Comment

💻 Day 18 of My 30-Day Golang Challenge! 🚀 Today, I explored middleware in Go—a powerful tool for adding key functionalities like authentication, logging, and more to web applications. Middleware streamlines and secures the process, helping create scalable, maintainable systems with minimal code duplication. 🟢 Day 18 Highlights: ♾️Seamless Integration: Middleware in Go makes it easy to layer in new functionalities, like access control or data validation. ♾️Enhanced Security and Logging: Essential features like user authentication, request logging, and error handling are simplified. ♾️Scalability for Large Applications: With middleware, Go applications become modular and more scalable, ready to support complex workflows. Excited to see how these tools can enhance both performance and security as I move forward in my Go journey! 💡 Let’s connect if you're working with Go middleware or backend development—always eager to share insights! #Middleware #BackendDevelopment #GoLang #30DaysOfGolang #SoftwareEngineering #WebDevelopment #TechLearning #coding #development #golang #linkedin #backend #frontend #Maang #Faang #scalable

10

You can learn Low Level System Design for FREE. Here’s how- ✅ Start with understanding what all you need to study for LLD. This step is optional and is for those who are absolute beginners. Here’s LLD Roadmap - https://lnkd.in/ggxTSBUa ✅ Learn basics of LLD, Understand UML Class Diagram and relationships between classes in detail - https://lnkd.in/g2ZYqeJN ✅ Learn Design Patterns - start with understanding what are design patterns, why are they important and then understand the common and important patterns. Here’s the playlist- https://lnkd.in/gTfR9qMf Now, you are ready to approach LLD of some common systems- ✅ Uber/ Ola LLD with explanation and code - https://lnkd.in/gDKz3UhK ✅ Swiggy/ Zomato LLD with explanation and code - https://lnkd.in/g4H7x3dj ✅ Zerodha LLD with explanation and code - https://lnkd.in/gXgAfY59 Save it and make sure you upskill and work on yourself. LLD will not only help you ace interviews but it will also make you a better software engineer. LLD is now expected from freshers as well. You just can’t not know this! 🤷🏻‍♀️💪🏼✌🏻 All the very best! Please share your progress as well 😇 #freeresources #lowleveldesign #softwaredevelopers

154

8 Comments

The coming weeks are are going to learn Terraform in 7.0 as it is one of the most common provisioning IAC in companies like Walmart Amazon Flipkart Atlassian etc. Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. The key features of Terraform are: Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used. Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure. Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure. Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors. If you are a fresher/Experienced and looking to upskill yourself, then do checkout the PRIME batch7.0 - 𝟏𝟒+ 𝐑𝐞𝐚𝐥 𝐓𝐢𝐦𝐞 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬 on DevOps and SRE - Highest CTC package of Rs. 𝟒𝟎 𝐥𝐚𝐤𝐡 𝐩𝐞𝐫 𝐚𝐧𝐧𝐮𝐦 in 6.0 batch - 𝟐𝟎𝟎+ 𝐑𝐞𝐚𝐥 𝐓𝐢𝐦𝐞 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞 - Roles and Responsibilities data with 𝐉𝐨𝐛 𝐒𝐞𝐚𝐫𝐜𝐡 𝐏𝐨𝐫𝐭𝐚𝐥𝐬 - Mock Interviews and Resume Reviews And the best part? Anyone who is a Fresher/Intern/working professional regardless of the industry they are working in is eligible for 𝐏𝐫𝐢𝐦𝐞 𝐁𝐚𝐭𝐜𝐡𝟕.𝟎. 𝐄𝐧𝐫𝐨𝐥𝐥 𝐏𝐑𝐈𝐌𝐄 𝐁𝐀𝐓𝐂𝐇 𝟕.𝟎-https://lnkd.in/gaRDBD4y [ 70% OFF ] 𝐂𝐡𝐞𝐜𝐤 𝟏𝟒+ 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬 𝐚𝐧𝐝 𝐏𝐥𝐚𝐜𝐞𝐦𝐞𝐧𝐭𝐬 - https://lnkd.in/gQg42c5E

376

20 Comments

AWS S3 Flaw : Bucket monopoly attack. One of the good and bad feature of AWS S3 service is that bucket-name is globally unique. Which means every S3 bucket name must be unique. With the development of IAAS (Infrastructure as code), many AWS services can create other AWS services if needed by them. Cloudformation is one of service that creates it's own S3 bucket to stores IAAS code (it does include ENV variables, IAM role and other sensitive data). The S3 bucket-name is quite predictable : "Predictable hash +[account-ID]-[region]" Now Imagine, one hacker can create lots of S3 bucket such that it matches someones cloudformation S3 bucket. Ideally cloudformation should fail since S3 bucket is in some other accounts. However cloudformation doesn't fails. As a result hacker now can get access to cloudformation metadata of some targeted user. This is known as "Bucket monopoly attack". Google it for more. It's a theoretical attack, but who knows. Follow Pushkar Kumar for more..

665

28 Comments

🚀Hey DevOps Enthusiasts! Today, I dived deep into Kubernetes RBAC and Authentication – a cornerstone of cluster security. Let’s simplify this powerful feature together! 💡 🔑 What I Explored Today: Roles & RoleBindings: For namespace-specific permissions. ClusterRoles & ClusterRoleBindings: For permissions across all namespaces. How Kubernetes ensures security through authentication (logging in) and authorization (working on resources). 🔐 Why is Authentication Important in Kubernetes? Kubernetes doesn’t directly create users but authenticates them through options like certificates, tokens, or proxies. I focused on client certificates for their simplicity and reliability. ✨ RBAC in Action Using Roles and RoleBindings, I assigned user-specific permissions to securely manage resources in a namespace. I also tested restricted actions to ensure the configuration worked perfectly. 💬 What’s Your Take? RBAC is essential for managing Kubernetes clusters securely. Have you tried configuring it in your environment? Let’s discuss and share insights below! #DevOps #Kubernetes #RBAC #CloudComputing #LearningJourney #Infrastructure #ScalingApps #TechInnovation #DevOpsCommunity #OpenSource #TechTips #TechJourney #DevOpsInnovation #TechSharing #DevOpsTools

17

Kubernets 1.31 now truly vendor neutral platform !! What is it mean and how things going to affect The release of Kubernetes 1.31 marks the culmination of a significant migration effort to remove in-tree cloud provider integrations. Previously, Kubernetes supported cloud providers like AWS, Azure, and Google Cloud directly within its core code, which created vendor dependencies, increased complexity, and bloated the system. With the removal of these in-tree integrations, Kubernetes now relies on external cloud controller managers (CCMs), requiring users to deploy them separately for each cloud provider. This transition was a massive undertaking, involving the development of new subsystems such as the kubelet credential provider and storage migration. The migration successfully reduced the Kubernetes core by 1.5 million lines of code and decreased binary sizes by 40%. While it simplifies future Kubernetes development and makes the platform more cloud-neutral, it may require organizations to adjust their existing configurations and scripts to accommodate these changes. Key takeaways: 1. Removal of in-tree cloud providers in Kubernetes 1.31 simplifies the platform but breaks backward compatibility for cloud-provider arguments. 2. Users must deploy cloud controller managers (CCMs) separately for cloud integration. 3. The migration cut code size significantly, making Kubernetes more lightweight and secure. 4. Organizations need to adapt to new deployment methods, especially with the updated kubelet behavior and external integrations. #Kubernetes #Devops #cloud #AWS #Azure #GCP #docker #Security

6

This week we are learning kubernetes from basics to depth :) What does Kubernetes do? 1) Deployment - Deploy a specified number of containers to a specified host and keep them running in a wanted state. 2) Rollouts - A rollout is a change to a deployment. Kubernetes lets you initiate, pause, resume or roll back rollouts. 3) Service discovery - Kubernetes can automatically expose a container to the internet or to other containers by using a domain name system (DNS) name or IP address. 4) Storage provisioning - Set Kubernetes to mount persistent local or cloud storage for your containers as needed. 5) Load balancing - Based on CPU usage or custom metrics, Kubernetes load balancing can distribute the workload across the network to maintain performance and stability. 6) Autoscaling - When traffic spikes, Kubernetes autoscaling can spin up new clusters as needed to handle the additional workload. 7) Self-healing for high availability - When a container fails, Kubernetes can restart or replace it automatically to prevent downtime. It can also take down containers that don’t meet your health check requirements. If you are looking for kubernetes projects do checkout my youtube channel - https://lnkd.in/gkB27ZDF Enroll for DevOps/SRE Classes - https://lnkd.in/gsryE-Bj Read this post till here, do share with your friends :)

762

21 Comments

Hi #everyone 🫵 A Simple Guide to Understanding Kubernetes Pods Give me 2 minutes of your time am going to tech you to How to Grasp #Kubernetes #Pods Easily ➡️ When you deploy an app , you deploy in a Pod in side #k8scluster ➡️ When you destroy an app , you terminate Pods form #k8scluster ➡️ When you scale up your app , you add more pods in #k8scluster ➡️ When you scale down your app , you remove pods form #k8scluster ➡️ When you update new version (V1 to V2) your app , you deploy new pods in #k8cluster 📌 Note: This make pods are more important and play important role in #Kubernetes cluster to deploy workloads 👉 A Kubernetes Pod is the smallest, most basic deployable unit in #Kubernetes cluster. It represents one or more tightly coupled #containers that share the same environment. ✅ Key Features of a Pod 🫵 Purpose of Pods: #Pods host application workloads, running one instance of your app or service. They ensure co-located #containers can communicate efficiently. 🫵 Multiple Containers (Optional): A Pod can contain one or more containers know as #multicontainerpods , Containers in the same Pod share: ➡️ Networking: They use the same IP address and ports. ➡️ Storage: They can share volumes for persistent storage. 🫵 Lifecycle Management: #Pods are designed to be ephemeral. If a Pod fails, #Kubernetes will replace it with a new one, but not "repair" it. Changes to a Pod require redeployment. 🫵 Networking: ➡️ Each Pod has a unique IP address in the Kubernetes cluster. ➡️ Containers within a Pod communicate via localhost. ➡️ Other Pods communicate using the Pod's IP. 🫵 Scaling: Pod #Horizontal scaling is achieved by creating more Pods not by adding more containers to a Pod. #Conclusion: Think of a #Pod as a single logical host for #containers running together. If multiple containers are in a Pod, they are like roommates sharing a house using same networking and storage 💁‍♀️ Are you confused with #Kubernetes documentation, refer https://lnkd.in/gxR8xUNj #KubernetesTraining #DevOpsJourney #ContinuousLearning #CloudNative #Containerization #InfrastructureAsCode #Automation #Microservices #CloudComputing #AgileDevelopment #DevOpsCulture #TechEducation #DigitalTransformation #CloudSkills #KubernetesCommunity #DevOpsExperts #LearningOpportunities #Innovation #TechTrends #CloudNativeDevelopment #ContainerOrchestration #DevOpsMastery #ContinuousImprovement #TechSkills #KubernetesCertification #DevOpsTraining

9

1 Comment

I am receiving interview calls from both MNCs and start-up companies, and recruiters have focused on advanced technical questions as well as situational scenarios related to #Kubernetes. These are some of the questions they have asked me in the interviews. 1.    How do you use Helm in Kubernetes? 2.    What is the difference between a DaemonSet and a Deployment? 3.    How do you handle logging and monitoring in Kubernetes? 4.    What strategies do you use for managing secrets in Kubernetes? 5.    How do you perform rolling updates and rollbacks in Kubernetes? 6.    How do you troubleshoot a failing Kubernetes Pod? 7.    What steps would you take to resolve a node issue in a Kubernetes cluster? 8.     How do you debug network issues in Kubernetes? 9.    A specific Kubernetes Pod is consistently failing after deployment. Describe your troubleshooting steps. 10. You notice that the response time of your application has increased significantly. How would you investigate and resolve this performance issue within Kubernetes? 11.  One of your nodes in the Kubernetes cluster has gone down. What steps would you take to ensure high availability and minimal disruption to your services? 12. How do you integrate Kubernetes with CI/CD pipelines? 13. What tools do you use for continuous deployment in Kubernetes? 14.  How do you automate Kubernetes cluster maintenance and updates? 15. Your team wants to implement canary deployments to gradually roll out new features. How would you set this up in Kubernetes? 16.  During a security audit, you find that your Kubernetes cluster is not compliant with security best practices. What steps would you take to secure the cluster? #openforwork #devops #kubernetesinterview #experince

12

AWS CloudWatch interview questions * *Basic Questions 1. What is Amazon CloudWatch? 2. What are the main features of CloudWatch? 3. What is a CloudWatch Metric? 4. How does CloudWatch collect data? 5. What are CloudWatch Alarms, and how are they used? 6. What is the retention policy for CloudWatch Logs? 7. What is a namespace in CloudWatch Metrics? *Intermediate Questions 8. What are CloudWatch Logs Insights, and how are they used? 9. How do you create a custom metric in CloudWatch? 10. What are CloudWatch Events, and how do they work? 11. How does CloudWatch differ from AWS CloudTrail? 12. What is the difference between basic and detailed monitoring in CloudWatch? 13. Can CloudWatch monitor on-premises servers? *Advanced Questions 14. How can CloudWatch be integrated with third-party tools? 15. How do you analyze large volumes of logs in CloudWatch efficiently? 16. What are metric filters in CloudWatch Logs? 17. Can CloudWatch trigger Auto Scaling actions? If so, how? 18. How do you optimize CloudWatch usage to reduce costs? 19. How does the CloudWatch Agent work, and what is its purpose? 20. What is the maximum number of metrics you can include in a CloudWatch dashboard? *Scenario-Based Amazon CloudWatch Questions 1. How would you monitor the CPU usage of an EC2 instance and get alerted when it exceeds a certain threshold? 2. How can you configure CloudWatch to automatically delete logs after 30 days? 3. What steps would you take to create a dashboard that shows metrics from multiple AWS services? 4. How would you monitor free disk space on an on-premises server using CloudWatch? 5. Your application logs contain both info and error logs, but you only want to monitor errors. How would you set this up in CloudWatch? 6. How can you monitor and set alerts for memory usage on an EC2 instance that is running out of memory frequently? 7. How would you trigger a Lambda function when an EC2 instance is started or stopped? 8. How can you use CloudWatch to scale resources dynamically based on high traffic during specific hours? 9. How would you monitor the number of API requests made to an S3 bucket? 10. Your CloudWatch Logs costs are increasing significantly due to high log volumes. What steps can you take to optimize costs? 11. How would you monitor and analyze the performance of containers running in an ECS cluster? 12. What steps would you take to troubleshoot delayed notifications from CloudWatch alarms? 13. How would you use CloudWatch to track the execution time of Lambda functions and get alerted for anomalies? 14. How can CloudWatch help you identify and respond to a sudden spike in read/write latency for an RDS database? 15. How would you configure CloudWatch to monitor custom metrics from your application? #AWSCloudwatch #DevOps #Interviewpreparation

48

안녕하세요, 여러분! 🚀 Day 13 of 30 Days Cloud Challenge ☁️: Seamless File Transfer Between S3 Buckets with AWS DataSync 📂🚀 Today, I used AWS DataSync to transfer files between two S3 buckets effortlessly. Here’s a quick breakdown of the steps: Step 1: Created two S3 buckets, source & destination, and loaded data into the source bucket. 📦 Step 2: Configured an IAM role for DataSync with permissions for both buckets to enable secure access. 🔑 Step 3: Set up a DataSync task in the DataSync Dashboard, selecting source and destination. 🚀 Step 4: Specified the IAM role in the task configuration to ensure DataSync could access the buckets. ⚙️ Step 5: Executed the task and monitored the transfer process in the console, confirming all files were successfully copied. ✔️ Using Amazon CloudWatch has significantly enhanced my ability to manage cloud resources effectively. Exploring the practical applications of AWS services like DataSync has been incredibly insightful. Thanks to my mentors Jey Aakash & Gokul M and AWS Cloud Club St.Joseph's Group of Institutions &PEP Cloud Computing (AWS/ Azure/ GCP) and DevOps Centre for inspiring me to continuously expand my AWS knowledge. Every day in this challenge brings new learning, and I’m thrilled to see where these skills will take me in real-world cloud projects! 🚀 #30DaysCloudChallenge #AWSDataSync #AWSS3 #CloudLearning #DataMigration #CloudJourney

18