Julio Rocha, FinOps Engineer Certified, FinOps Practitioner, Multicloud,

Best CI/ CD Tools Part1 𝐆𝐢𝐭𝐋𝐚𝐛 𝐂𝐈/𝐂𝐃 It is a software development platform for managing different aspects of the software development lifecycle. With its cloud-based CI and deployment service, this tool allows developers to trigger builds, run, tests, and deploy code with each commit or push. GitLab CI/CD also assures that all code deployed to production adheres to all code standards and best practices. 𝐾𝑒𝑦 𝑓𝑒𝑎𝑡𝑢𝑟𝑒𝑠 •   Direct connection with Kubernetes for efficient application deployment and scaling •   Automatic security scans for compliance and vulnerability checks •   Seamlessly integrate with third-party platforms including Slack, Asana, ClickUp, Notion, and Trello •   Real-time managing collaborative projects and tracking progress •   View, create, and manage codes and project data through branching tools 𝐆𝐢𝐭𝐇𝐮𝐛 𝐀𝐜𝐭𝐢𝐨𝐧𝐬 GitHub Actions is a comparatively new tool for performing CI/CD. It automates, customizes, and executes software development workflows right in the repository. GitHub Actions can also be paired with packages to simplify package management. It creates custom SDLC workflows in the GitHub repository directly and supports event-based triggers for automated build, test, and deployment. 𝐾𝑒𝑦 𝑓𝑒𝑎𝑡𝑢𝑟𝑒𝑠 •   Fully integrates with GitHub •   Built-in secret store •   Include multiple CI templates or can create one •   Live log feature offers insights into real-time workflow run •   Support matrix build i.e. runs the same job with multiple configurations 𝐉𝐞𝐧𝐤𝐢𝐧𝐬 Jenkins is the first CI/CD tool that provides thousands of plugins to support building and deploying projects. It is an open source as well as a self-hosted automated server in which the central build and continuous integration take place. This tool can also be turned into a continuous delivery platform for any project. It is usually an all-rounder choice for the modern development environment. 𝐾𝑒𝑦 𝑓𝑒𝑎𝑡𝑢𝑟𝑒𝑠 •   Simple and easy UI •   Seamlessly integrate with major cloud platforms such as Azure, Google Cloud, Amazon web services, Slack, and Digital Ocean •   Jenkin’s feature ‘Master-Slave Architecture’ helps in efficient resource usage •   Real-time testing and reporting •   1500+ plugins and run by a high-paced community #CI/CD #𝐆𝐢𝐭𝐋𝐚𝐛 #𝐆𝐢𝐭𝐇𝐮𝐛 #𝐉𝐞𝐧𝐤𝐢𝐧𝐬

5

Cloud Deployment on AWS: Docker, Terraform, and Deployment with Fargate.. #aws #cloud #docker #terraform

12

Just finished the course “Kubernetes: Your First Project” by Carlos Nunez! Check it out: https://lnkd.in/dJSff5NM #kubernetes.

6

Kubernetes v1.31 is generally available on Amazon EKS! 🎉 https://lnkd.in/dVzTU4cB Not sure if this pure coincidence, but today starts the KCD Porto. A great news to share with our local community in #Portugal. #kubernetes #containers #aws #eks

80

Neste vídeo iremos ver como instalar e configurar o Ingress Istio. https://lnkd.in/drFx9sQ2

10

Erro RMAN-07540: Cleanup is required for the VPC user schema ao conectar no catalogo do ZDL Recovery Appliance

12

Improving my cloud skills.

4

Well this post made me recheck my unused AWS account and provisioned resources (and thanks Maciel Pocwierz for sharing this insight). It shows one of the cloud service weaknesses is that they can be missused by malicious actors and cause you a headache. #aws #s3 #cloudcostbilldepletionattack

5

6 comentários

AKS - Azure Kubernetes Baseline architecture of an AKS cluster, for all professionals who are starting their journey at AKS and building their first projects. Below is a file prepared based on practices recommended by architecture and the Azure Well-Architected Framework, which guides interdisciplinary teams or several different teams (networking, security and compliance). #aks #cloud #azure #devops #terraform #iac #kubernetes

5

🚀 Just Completed: "Jenkins and Docker: Continuous Delivery Pipeline" Course! 🛠️🐳 Exciting update! I've successfully wrapped up the "Jenkins and Docker: Continuous Delivery Pipeline" course on Alura with Rafael Zago as the instructor, delving into the world of continuous integration and delivery with Jenkins and Docker. 💻 Here's a glimpse of what I've learned: 1. **Understanding Continuous Delivery Concepts** 🌐   - Explored the principles and benefits of continuous delivery for streamlining software development and deployment. 2. **Setting Up Jenkins Pipelines** 🚀   - Mastered the configuration of Jenkins pipelines to automate the build, test, and deployment processes. 3. **Containerization with Docker** 🐳   - Learned about Docker and its role in containerization, enabling consistent and portable environments for application deployment. 4. **Integrating Jenkins with Docker** ⚙️   - Explored methods for integrating Jenkins with Docker to create efficient and scalable continuous delivery pipelines. This course has been instrumental in enhancing my understanding of CI/CD practices and tools, empowering me to build robust and reliable delivery pipelines. A huge thank you to Alura for the comprehensive content and hands-on exercises! 🙌 Excited to apply these skills in real-world projects and contribute to efficient software delivery. Let's continue our journey of mastering CI/CD together! 👩‍💻👨‍💻 #Jenkins #Docker #ContinuousDelivery #CI/CD #DevOps #AluraCourses #TechSkills #CodeNewbie #ContinuousLearning #TechCommunity #DigitalEducation #CareerDevelopment #TechLearning #ProfessionalGrowth

12

1 comentário

Disaster recovery refers to the ability to restore your systems after a catastrophic event. There are four common types of disaster recovery strategies, each with its advantages and trade-offs: 1. Backup and Restore This is the most basic and widely used option for data recovery. Backups are regularly taken, and in the event of a disaster, you restore the data from these backups. Cost: $ (Lowest)    Storage costs for backups (e.g., cloud storage like AWS S3, Google Cloud Storage) RTO: Hours to days (8-72 hours depending on the size of data and recovery process)    This is the slowest recovery option, as you need to manually restore from backups. 2. Pilot Light This approach keeps a minimal version of your system running in a secondary region. In the event of a disaster, you scale it up to take over full functionality. Cost: $$ (Moderate)    Only minimal infrastructure is running, but costs rise with scaling when needed.    Example: Keeping database schemas or core services active, but inactive traffic handling. RTO: Minutes to a few hours (30 minutes to a few hours)    You need time to scale the infrastructure to production levels. 3. Warm Standby With Warm Standby, you maintain a scaled-down but running version of your system in another region. Traffic is only routed to this region if the primary system fails. Cost: $$$ (Moderate to High)    A reduced but running system incurs ongoing costs, though less than full-scale production.    Example: Running a smaller server instance, database replication, or reduced capacity. RTO: Minutes to an hour (5-30 minutes)    Requires minimal configuration to redirect traffic or scale up the system. 4. Active-Active In an Active-Active setup, full versions of your system run in multiple regions, sharing the load between them. If one region fails, the other continues to serve traffic without any disruption. Cost: $$$$ (Highest)    You maintain full operational infrastructure in multiple regions, incurring higher ongoing costs.    Example: Running fully mirrored production environments across multiple regions. RTO: Near-zero (seconds to minutes)    Fastest option with little to no downtime, as both systems are live and traffic is already distributed. Additional Metrics Recovery Point Objective (RPO): The point in time to which you can recover data (i.e., the amount of data you might lose in the event of a disaster). This ranges from minutes (Active-Active) to hours/days (Backup and Restore). Cost of Downtime: For businesses, downtime costs can range from $100,000 to $1 million per hour, depending on industry and business size, which makes faster recovery times critical for highly-available systems. https://lnkd.in/d9esdDT3 https://lnkd.in/dgbVMgdU #AWS #Cloud #DisasterRecovery

11

1 comentário

A big thank you to Daniel de Souza Casali for sharing his insightful blog on installing the OpenShift Container Platform quickly on PowerVS while using the Cloud private DNS. This method allows you to use your Enterprise Domain Name Server instead of creating a new domain or subdomain for the Cloud. https://lnkd.in/ervquC34 Topics covered in Daniel's blog 1) Configuring the IBM Cloud account for the Installation 2) OpenShift Installation 3) Preparing the install host for the OpenShift installation 4) Configure the Enterprise DNS for API access 5) Publish your Default ingress controller Privately (Recommended) 6) Optional – Publish your default ingress controller publicly. 7) Using a secondary ingress controller for public applications

14

Dedicated time: 7 hours 45 minutes Continuous learning is essential. That’s why I’m excited to share I’ve earned my Optimize Costs for Google Kubernetes Engine Skill Badge #GoogleCloudLearning #GoogleCloudSkillBadge

9

Are you looking for a way to streamline your Docker container deployments? Check out this tutorial on how to automate the process with Azure Pipelines. The tutorial covers each step in detail, starting with setting up your Azure DevOps project. You'll learn how to manage your work items with Azure Boards, create your Azure App Service environment, and create pipeline variables in Azure Pipelines. To ensure secure authentication, the tutorial also walks you through creating a service connection to authenticate with your Azure subscription. Automating your Docker container deployments has never been easier. Give it a try and let us know what you think! #Azure #Docker #DevOps #Automation

35

2 comentários

🚀Exploring Cloud Resource Optimization: The Brazilian Challenge In today’s rapidly evolving tech landscape, cloud resource allocation is a key component of operational efficiency. However, in high-interest-rate environments like Brazil, traditional optimization methods fall short of delivering sustainable results. After exploring various strategies to optimize the use of non-managed VMs and managed DBs through long-term commitments and horizontal scaling, the results showed a consistent roadblock: operational efficiency alone does not guarantee positive Free Cash Flow (FCF) when considering currency risks and opportunity costs. 🔑 Key findings: 1.Even with flexible cloud resource allocation strategies, Brazil's economic conditions limit the effectiveness of pure operational optimization. 2-Innovation plays a critical role in enhancing productivity, meaning government intervention and corporate initiatives are essential to improve the country’s technological capacity. 3-Strategic financial planning and a broader stakeholder alignment are required to navigate these challenges effectively. This tool was built for educational purposes, and you can check out the full blog post and code on my GitHub. Feel free to explore the model and its applications! How are you balancing cloud efficiency with macroeconomic challenges? Let’s discuss how technology and innovation can help bridge that gap. #CloudComputing #Optimization #Innovation #BrazilEconomy #CloudStrategy #FinOps

11

4 comentários

AWS Practitioner training very good platform to improve your knowledge AWS Skill builder

11

I'm really happy to share that I've earned the HashiCorp Certified: Terraform Associate certification! I believe Terraform knowledge is indispensable for Cloud Engineers as it enables Infrastructure as Code (IaC), multi-cloud provisioning, automation, scalability, and ensures consistency and standardization in cloud deployments. I'm grateful for the support from KodeKloud during my preparation, especially through their Free Week program. 🙏 I'm really a fan of their approach of combining lectures with hands-on labs and it was incredibly helpful in mastering Terraform. #HashiCorp #HashiCorpCertification #Terraform #CloudComputing

103

8 comentários