Pablo Daniel Martinez

Hi friends! Sharing the following Blog post I wrote about a very cool utility I helped develop here at my current job @ CloudEQ. Hope you like it and hope you can share it with your SRE peers using New Relic! =)

11

2 comentarios

Completed the Grafana Observability Solution Architect Course

41

3 comentarios

View my verified achievement from @GitLab! #GitLabCertifiedProjectManagementAssociate #DevOps #GitLab #ContinuousIntegration #ContinuousDelivery #ContinuousDeployment #CICD #ContinualLearningAndExperimentation

18

4 comentarios

Monte Verde (HTB Medium) Today's lab folks. Leveraging null/anonymous access on RPC and LDAP to enumerate users and organizational structure. Getting initial access due to weak password policy. PrivEsc by abusing intended functionality of Azure AD Connect.

3

🚀 Design Patterns for Extensible Kubernetes Controllers An insightful talk by Rafael Fernández López and Fabrizio Pandini titled “Kubernetes is Your Platform: Design Patterns for Extensible Controllers”. Key Takeaways: 🔹 Complexity in Extensions: As Kubernetes adoption grows, developers often need custom controllers. When business logic becomes too complex, extending controllers becomes essential. 🔹 Design Patterns to Know: 1️⃣ Controller Watching the Same Object: • Example: A Machine controller manages machines, while a VolumeBackup controller watches the same machine to perform backups before deletion. • Benefit: Separates concerns without overcomplicating the primary controller. 2️⃣ Parent-Child Controller Relationship: • Example: A Deployment controller creates ReplicaSets, and a ReplicaSet controller manages pods. • Benefit: Enables scalability and advanced features like rollbacks. 3️⃣ API Contract Pattern: • Example: A generic Machine controller interacts with various infrastructure implementations (AWS, Azure) through a minimal API contract. • Benefit: Allows swapping implementations without changing core logic. 🔹 Extending a Single Controller: • In-Process Extensions: • ⚙️ Efficient but may introduce security risks. • Out-of-Process Extensions: • 🔒 Improved security and flexibility but adds complexity. Looking Forward: ✨ Community Collaboration: There’s a need to standardize how we extend controllers. 📌 Challenges Ahead: Documenting dependencies, enhancing debuggability, and defining clear extension contracts. Final Thoughts: This talk highlighted the importance of design patterns in managing Kubernetes’ complexity. Embracing these patterns and collaborating as a community is vital for future growth. 💡 Have you used these design patterns in your Kubernetes projects? Share your experiences! #Kubernetes #CloudNative #DesignPatterns #OpenSource #suse #vmware 🚢

13

Una nueva publicación Configuring “EC2 Image Builder” with Terraform and automating the creation of a new AMI with Linux (AL2, AL2023, Ubuntu): 😁 https://lnkd.in/gr9eHcuU #Linux #AWS #Terraform #Devops #SRE

2

Just finished the course “Azure Microservices with .NET Core for Developers” by Rodrigo Díaz Concha! Check it out: https://lnkd.in/eH9Mb4q4 #microservices #netcore #clouddevelopment #microsoftazure.

4

VagrantVM A nice way to get started with virtualization and actually with IaC https://lnkd.in/dhWsRQnE #vagrant #devops #aws #IaC #wmware #cloud

1

Getting started with Valkey and Finch por Ricardo Sueiras . Check out the GitHub repo for the code and give it a try! #Valkey #OpenSource #Docker #Finch #DeveloperCommunity https://buff.ly/3yae5F6 #aws #cloudcomputing

1

I am excited to announce that I have recently passed the Certified #Kubernetes Administrator (#CKA) exam! Tips: * Get familiar with imperative commands. `kubectl` can save you a bunch of time when solving scenarios. * You get two simulator sessions when buying the exam, make good use of both of them. They are more difficult than the real exam, and most likely, you won't complete all questions in the given time. However, go through all the questions as they should give you a really good level to pass the exam. * killer.sh also has a bunch of scenarios quite similar to the real exam; the platform is free, so try them. * I didn't have much problem with the PSI browser, but make sure you log in 30 minutes before to set your environment and clean your desk/room so you streamline the proctor verification.

21

4 comentarios

💡Know what's news blog about AWS! 🔍 💡¡Conoce los nuevos blogs en AWS! 🔍 Streamline container application networking with built-in Amazon ECS support in Amazon VPC Lattice #awsnews #aws #news #whatsnew #tech #womantech

1

Kubernetes and Terraform Together Combining Kubernetes and Terraform takes operations to the next level: Comprehensive Management: Terraform can manage both the underlying infrastructure (networks, storage) and the deployment of applications in Kubernetes, offering a comprehensive solution. Operational Efficiency: It simplifies the management of infrastructure and application deployment, allowing the DevOps team to focus on more strategic tasks. Security and Compliance: Define policies and configurations in code, ensuring that security best practices and compliance are consistently applied across the entire infrastructure. #k8s #DevOps #AWS #terraform

8

2 comentarios

DVA is not associated with this job post. GCP DevOps Engineer, Colombia https://lnkd.in/gQxPt6uB You will be accountable for the following responsibilities: Write Terraform configurations to represent the GCP infrastructure state in code. Represent the actual infrastructure in network/topology/services diagrams in each environment (Development, QA, Production) Plan and conduct game days to test and enhance the code and diagrams. Propose the best practice approaches in terms of architecture design, security, naming conventions, governance, etc. Support CI/CD lifecycle Take ownership of the environment assigned. #jobposting #jobs #jobsearch #job #hiring #jobopening #jobhunt #recruitment #jobsearching #employment #jobvacancy #jobopportunity #jobseekers #jobfair #nowhiring #jobshiring #jobinterview #recruiting #career #jobseeker #jobhunting #jobalert #careers #hiringnow #work #joblisting #jobopportunities #jobvacancies #jobseeking #dreamjob

2

🌟 Harnessing the Power of Kubernetes Selectors 🌟 In Kubernetes, selectors are a powerful tool that allow you to manage, organize, and automate the behavior of resources across your cluster. Selectors act like filters, helping you target a specific set of resources based on labels. By defining selectors, Kubernetes can match and operate on a subset of resources that share common characteristics. This makes operations like updates, scaling, and service discovery more efficient and precise. 📌 Why Does This Matter? Selectors are essential for: - Efficient resource management : Choose specific Pods or Deployments based on labels, ensuring the right resources are targeted. - Automation : Automate scaling, updates, and rollouts to specific sets of resources, improving both precision and speed. - Service routing : Route traffic to the correct set of Pods, such as directing a web service only to Pods labeled `role=frontend` and not to backend Pods. 🎯 Real-World Example Imagine you have multiple Pods running different services in your application. By using label selectors, you can: - Update only the Pods labeled `version=v2` during a rolling update. - Scale the `frontend` service independently from the `backend`. - Route traffic via a Service to Pods labeled `tier=frontend`. Selector Example: yaml spec:  selector:   matchLabels:    app: nginx This selector ensures that only Pods with the `app=nginx` label are targeted by the deployment. By leveraging selectors, Kubernetes helps your team focus on the right resources at the right time—driving operational efficiency and agility in your cloud infrastructure. It’s the key to scaling and managing complex workloads with ease! 🚀 #Kubernetes #DevOps #CloudComputing #Automation #CloudNative #Microservices #TechInnovation #Infrastructure

3

#ReplicaSets 🌹 "Unlock the Power of ReplicaSets : Kubernetes' Secret to Scalability and High Availability!" Hey K8s rockstars! Are you ready to take your Kubernetes game to the next level? Let's dive into ReplicaSets, the unsung heroes of K8s! What is a ReplicaSet : A ReplicaSet ensures a specified number of replicas (identical Pods) are running at any given time. It's the next-generation replacement for Replication Controllers (RCs)! Mind-Blowing Features: 1. Set-based selection: Select Pods based on labels, annotations, and more! 2. Flexible scaling: Scale up or down with ease, using numeric or percentage-based updates! 3. Automatic restart: Failed Pods are restarted, ensuring zero downtime! 4. Self-healing: Replace terminated or deleted Pods automatically! 5. Integration with Deployments: Seamless rollouts and rollbacks! Benefits: 1. High availability: Ensure continuous application availability! 2. Scalability: Scale with ease, without manual intervention! 3. Fault tolerance: Automatic recovery from node failures! 4. Efficient resource utilization: Optimize resource allocation! Use Cases: 1. Stateless applications: Scale web servers, APIs, and microservices! 2. Stateful applications: Ensure data redundancy for databases! 3. Machine learning: Scale training and inference workloads! Best Practices: 1. Define clear labels: Ensure accurate Pod selection! 2. Set replica counts: Balance resource utilization and availability! 3. Monitor ReplicaSet performance: Adjust replica counts as needed! Comparison with Other K8s Objects: 1. Replication Controllers: ReplicaSets offer more advanced features! 2. Deployments: ReplicaSets are the building blocks for Deployments! Takeaway: ReplicaSets are the key to unlocking scalability, high availability, and fault tolerance in Kubernetes! Share your ReplicaSet experiences! What challenges have you overcome? #ALNAFI##Kubernetes #ReplicaSet #Scalability #HighAvailability #DevOps #CloudNative 🌹

1

Some of new tools in DevOps 😎 1.Pulumi: A modern infrastructure as code tool that allows you to write code in familiar programming languages like Python, JavaScript, or Go to define and manage cloud infrastructure. 2.Tekton: A Kubernetes-native framework for creating CI/CD systems. 3.Crossplane: An open-source project that provides a way to manage cloud infrastructures through Kubernetes. and NOW YOU: In the continuation of this article, introduce some new tools??? 😉 #DevOps #CloudSecurity #Infrastructure #SecurityBestPractices #CloudAdoption #AWS #AZURE #DEV_SEC_OPS #DEVSECOPS #new_tools

6

hadolint/hadolint: Dockerfile linter, validate inline bash, written in Haskell

1