Thiago Cesar Calori Esteves’ Post

🚀 Simplifying External Access in Kubernetes with NodePort! 🚀 Need to expose your services to the outside world in Kubernetes? NodePort is here to help! By mapping a port on each node of your cluster, NodePort makes it easy to access your application externally via <Node_IP>:<NodePort>. 🔑 Key Highlights: Exposes services outside the Kubernetes cluster. Supports custom port selection within the range 30000-32767. Access your service via any node's IP and NodePort, from anywhere! Whether you're managing web apps like Nginx or Apache, NodePort simplifies traffic routing in your cluster. Have you tried NodePort in your setup yet? Let’s discuss how it’s working for you! #trainwithshubham #90daysofdevops #Kubernetes #DevOps #NodePort #K8sNetworking

Do you know Keel in the Kubernetes ecosystem ? #kubernetes Github : https://lnkd.in/eCtXGbfw Official Website : https://keel.sh/ Keel is a very useful tool to follow and handle image versions into : helm charts, deployments, daemonsets, statefulsets... A little tool which can help you to maintain your kubernetes clusters and its tools. Because kubernetes solve a part of the main problem (how to upgrade smoothly your apps) but it's another hard task to follow your versions and activate a change. In the same way, you can discover Renovate another great tool to admin your cluster > https://lnkd.in/emTZds22 Enjoy !! #devops #opensource

🚀 Day 6: GET APIs for Transactions & Users – Connecting the Dots! 🚀 Another milestone hit today in our collaborative project with Vipin Sain! We focused on building out key GET APIs to link transactions and users, pushing our backend development forward. 🎯 Here’s what we worked on: 🔍 API to Find a User from a Transaction: I created an API that allows us to retrieve the associated user of any given transaction. This is crucial for maintaining accurate user data and ensuring that every transaction is linked back to the right individual. 🔄 API to Find Transactions from a User: Vipin Sain built an API that fetches all transactions tied to a specific user. This will be super helpful for tracking user activity and generating detailed reports. These two APIs form the backbone of our data retrieval system, enabling smooth interactions between users and their transactions. 🌐 📂 GitHub Repo: Curious to check out the code? Follow our journey here: https://lnkd.in/giNQhveg 📂 Big thanks to Vipin Sain for building out the user-to-transaction functionality while I tackled the reverse! We’re getting closer to a fully functional backend—stay tuned for more updates! #Day6 #APIDevelopment #MERNStack #BackendDevelopment #Transactions #MongoDB #GitHub #SoftwareDevelopment #CollaborativeProject #TechInnovation #LearningJourney

Two exciting new features in the #Terragrunt 🤌🚀 terragrunt catalog: Allows you to treat all the modules you use across a variety of Git repos as a single, unified, searchable, module catalog. terragrunt scaffold: Command generates code for you, either from Terragrunt’s default template, or a custom Boilerplate template of your own, making it easier to configure modules for deployment, and to standardize your coding patterns. Put these two together, and you’ll be able to accelerate the adoption of Infrastructure as Code (IaC) and developer self-service patterns in your organization. #iac #sre #devops #platformengineering #terraform #terragrunt #opentofu

We are happy to share that our application 𝐍𝐞𝐚𝐫 𝐫𝐞𝐚𝐥-𝐭𝐢𝐦𝐞 𝐨𝐫𝐝𝐞𝐫 𝐭𝐫𝐚𝐜𝐤𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 𝐀𝐏𝐈 𝐆𝐚𝐭𝐞𝐰𝐚𝐲 𝐖𝐞𝐛𝐒𝐨𝐜𝐤𝐞𝐭 𝐚𝐧𝐝 𝐀𝐖𝐒 𝐒𝐭𝐞𝐩 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐬 is now available on Serverless Repo. Starting the execution of a Step Functions workflow directly from WebSocket APIs 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐫𝐞𝐪𝐮𝐢𝐫𝐢𝐧𝐠 𝐦𝐢𝐝𝐝𝐥𝐞𝐰𝐚𝐫𝐞 𝐜𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 𝐥𝐢𝐤𝐞 𝐀𝐖𝐒 𝐋𝐚𝐦𝐛𝐝𝐚. This helps optimize the cost and reduces the operational overhead by not relying on multiple components. Links: 🔹 https://lnkd.in/gG7FkTDP 🔹 https://lnkd.in/gFADwbiw I would like to thank Bharat Sahni for being an amazing companion. [We started it before re:Invent last year and somehow managed to prioritize this in Feb, 2024]. Now, after a number of reviews and revisions, here we are. 😃 Please feel free to check this out and share your thoughts/feedback. We would also want to thank James Beswick for his guidance on this content. He always ensures that quality remains intact for our readers. 📖 #content #serverless #websockets #apigateway #stepfunctions #dynamodb #repository #training #public #awscloud #serverlesscomputing #serverlessarchitecture

🚀 Excited to share my latest practice project! 🎉 Title: Deploying a 3-Tier App on Kubernetes with Docker and Helm Just completed a practice project where I deployed a 3-tier application (React, Node.js, MongoDB) on a Kubernetes cluster using Docker and Helm. Here are the key steps: Gained hands-on experience with: 🐳 Containerizing apps with Docker 📤 Pushing Docker images to a registry 🛠️ Packaging and deploying apps to Kubernetes using Helm 🔧 Configuring Kubernetes resources 💻 Working with local Kubernetes clusters Check out the GitHub repository for the complete walkthrough: [https://lnkd.in/dVZkg-K6] #Kubernetes #Docker #Helm #DevOps #ContainerizationPracticeProject

🚀 New Blog Alert! 🚀 Get started with Docker and dive into the fundamentals of containerization! If you're new to Docker or looking to refresh your skills, this blog covers everything from installing Docker to building and managing your first containerized app. Learn about Docker's architecture, core commands, and how to deploy applications with ease using Docker Compose. Unlock the power of Docker for streamlined development and efficient deployment! 💻🌐 Read the full blog here: https://lnkd.in/gzExkqfP #Docker #Containerization #GettingStarted #DevOps #TechBlog #CloudComputing #Deployment #DeveloperTools #Microservices #TechTrends

Ever wondered how NGINX revolutionizes application delivery in this era of digital transformation? Join us and NGINX's team of experts to find out on March 14th at 3 PM IST in an exclusive webinar. Don't Miss Out On: 1. Enterprise-Grade Integration: Experience NGINX's impact on scalability, reliability, and agility in your architecture. 2. NGINX Unleashed: Uncover the versatility of NGINX as your go-to platform for web app delivery. 3. Versatile Solution: See how NGINX effortlessly handles diverse requirements. 4. Real-world Insights: Delve into practical NGINX applications with insightful use cases. 5. Live DEMO: Witness NGINX in action and gain hands-on implementation insights. and much more REGISTER HERE 👉  https://bit.ly/431j4TD #NGINX #webinar #applicationdelivery #kubernetes #DevOps #SolutionArchitect #OpenSource #india #webinarseries #webinaralert Anushya Prakash Bharat Merja Bhavya Upadhyay Raghavendra Yadav Sachhin Dabir Ravi Papnoi Sahil Alva Abhishek Singh Bhadouria

🤔 𝐂𝐮𝐫𝐢𝐨𝐮𝐬 𝐚𝐛𝐨𝐮𝐭 𝐜𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐢𝐳𝐚𝐭𝐢𝐨𝐧? 📦 Imagine your app is like a moving box. You’ve packed the essentials (code), but you also need to include the fragile items (libraries, runtime environment, configuration files) to make sure everything arrives safely. #Docker is your sturdy, well-organized moving box that keeps all your software components secure and intact, ready to be unpacked and run anywhere—no broken pieces, no missing parts. 🐳🎯 Ready for a quick Docker 101 lesson? From key commands to core concepts, find it all here: https://lnkd.in/gsGH-sjj #Containerization #AIinDevOps #DevOpsAutomation #Microservices #MachineLearningOps #CloudNative #InfocuspInnovations

Pods in Kubernetes. ⇢ A Hands-On Example with Kubernetes Pods. In Kubernetes, a Pod is the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a single instance of a running process in your cluster. Key Components of a Pod: 1. Containers: The application or process to be run. Containers in a Pod are usually Docker containers. 2. Storage Volumes: Shared storage for containers in the Pod. 3. Networking: A unique IP address for each Pod, and all containers within a Pod share the network namespace. Pod Lifecycle: 1. Pending: The Pod has been accepted by the Kubernetes system, but one or more of the containers has not been created. 2. Running: The Pod has been bound to a node, and all of the containers have been created. At least one container is still running or is in the process of starting or restarting. 3. Succeeded: All containers in the Pod have terminated successfully, and will not be restarted. 4. Failed: All containers in the Pod have terminated, and at least one container has terminated in failure. 5. Unknown: The state of the Pod could not be obtained, usually due to a communication error. In this blog, I've explored the pod concept in Kubernetes, along with a practical example that demonstrates their usage. 🔗 Read the full blog: https://lnkd.in/di_xVBDr Please feel free to spread information about this blog to your network if you find it useful. Your peers and colleagues might find the information about Kubernetes pods useful. I appreciate you sharing this information.