Boran Şeref

Remember ELK stack? Meet OTEK stack (OpenTelemetry + Elasticsearch + Kibana)! Join me at the Elastic Meetup in Kraków, Poland on October 21st to talk about #OpenTelemetry and #Elasticsearch, and how many more acronyms we can handle.

34

Use terraform fmt for Consistent Code Formatting Why? Keeping your Terraform code consistently formatted improves readability and makes collaboration easier. The terraform fmt command automatically formats your configuration files to follow a standard style, eliminating inconsistencies like misaligned indentation or mixed tabs and spaces. How to Use: Run terraform fmt in the root directory of your Terraform project This command will automatically format all .tf files in the current directory and its subdirectories. Benefits: Consistency: All Terraform code looks uniform, which reduces errors and makes it easier to review. Collaboration: When everyone uses the same formatting, merging changes becomes smoother, with fewer conflicts. How do you ensure your Terraform code remains clean and consistent? Do you rely on terraform fmt, or do you have other strategies or tools in your workflow? Share your tips and tricks for maintaining code quality! Consider a repost if you like this post. Please follow Arbaz Mohammed for more such tips. #Terraform #Devops #Cloud #Azure #Aws

1

Next AWS User Group Wrocław meetup in a week (24.04.2024). 📅 24.04.2024 ⌚ 18:00 📍 Wędrówki Pub: https://lnkd.in/eeYukrXZ First of all, thank you ALGOTEQUE Innovation Hub for sponsoring our event! :) 🎤 Speakers: 🔭 Marcin Sodkiewicz (me) I am going to talk about #opentelemetry in my talk titled "Observability on AWS & OpenTelemetry". It's talk on the 300 level, but don't worry, I am going to cover all areas, and even if you are new to a whole concept I think you should understand everything. This is also a great opportunity to discuss your experiences with #opentelemetry. 📟 Grzegorz Kalwig: "Serverless is above limits? Our Path to production database cluster" If you don't know about it - Grzegorz is on a road tour with that talk as I believe I saw that he presented that material in many User Groups already. It means that his material is polished and he should be able to answer all your questions about Aurora Serverless v2. Super interesting and important topic, so stop by and make notes :) We are still part of JetBrains Community Support program. So we are going to give away some coupons for free access to IDE of your choice for a whole year. More details: https://lnkd.in/egGjACeV #awscommunity #awsugwro #opentelemetry #aws #rds #auroraserverless #serverless

13

1 komentář

Many tutorials I have come accross seem to focus on how things work and ignore how they fail. Recently, I experienced a lot failures while playing ⚽️ with containerizing Netflix 's Eureka Server, so I decided to document how it all failed and how I fixed it. The main issue was the outdate docker image, so I had to rebuild it from scratch. 🔍 Here are the steps I took 👇🏾 https://lnkd.in/e8F8DKjx #devops #opensource #docker #netflixoss #netflix #ZeroToDocker

4

2 komentáře

In my previous post https://lnkd.in/daZayXZG, we deployed the Terraform Management Console app in a VM. Now, how can we ensure that our application is always running healthy all the time? The answer is observability. By implementing observability, we can monitor our app’s health by collecting and storing application logs and infrastructure metrics in a monitoring tool that allows us to visualize them. Our observability setup has two main components: 1. Log Collection: I used Promtail agent to collect logs from various sources. These logs are then stored in Loki, which serves as a data source for Grafana to visualize the logs. 2. Metric Collection: For metrics, I used node-exporter to expose VM-level metrics on port 9100. These metrics are collected by Prometheus, which serves as a data source for Grafana to visualize the metrics. Grafana acts as our main tool for monitoring and alerting. I've attached a video that walks through the entire setup and implementation. Check it out and let me know your thoughts! Please find the config files here: https://lnkd.in/dcZA7nMh #SRE #Monitoring #Observability #Logging #DevOps

32

🔭 OpenTelemetry Collector: The Architecture Review I have just published the second article in my OpenTelemetry series about design, architecture and interesting implementation spots in the OTel Collector including: - 🔗 The Signal Processing Pipeline Architecture -📡 OTel Receivers. Prometheus-style Scrapers - ⚙️ OTel Processors. The Memory Limiter & Batch Processor. Multi-tenant Signal Processing - 🚚 OTel Exporters. The Exporting Pipeline & Queues. The implementation of persistent queues - 🔭 How observability is done in the OTel Collector itself. Logging, metrics, and traces - 🔌 OTel Extensions Design. Authentication & ZPages -👷Custom Collectors & OTel Collector Builder - 🚧 Feature Gates Design & The Feature Release & Deprecation Process Enjoy the article & let me know how do you like it 🙌 #observability #opentelemetry #golang #distributedsystems

17

3 komentáře

Terraform outputs are a powerful feature that enhance modularity, reusability, and ease of management. https://lnkd.in/dDQhKW8w

14

#ApacheKafka 3.8 is here, and features 17 new KIPs: ● 13 related to Kafka Core and clients ● 3 for Kafka Streams ● 1 for Kafka Connect In this new video, Danica Fine]provides a summary of the latest updates and new features in this Apache Kafka release! Watch it here ➡️

1

One of my beefs with terraform is it’s trying so hard to be flat. Some of us want very dynamic scripts. But when you create a k8s cluster, form the kubexonfig file, then need to use the kubexonfig file to load in the rest of the parts like ingress, having a depends_on would be nice for providers. I did cheat a little and abuse the variable system to force the provider to wait, but then you run into what about a workspace that will have kubernetes set to false and get a zero count for your k8s module? Then it gets angry because the module output isn’t there. I still like Chef. Chef let me do what I want when I want. Just was bad on creating the underlying infrastructure but great at configuring it once it was up. *shrug* #terraform #kubernetes #k8s #eks #automation #burgerkingmodel

3

1 komentář

📢 Big news! Kong Inc. Ingress Controller 3.2 is out now! 📢 This update brings incredible new features such as Fallback Configuration and Custom Entities, enhancing flexibility and reliability in managing your Kubernetes environments. At Kong, we prioritize our customers and continuously push the boundaries of technology. Proud to embody our core values of being CUSTOMER CHAMPIONS and OWNERS. Great blog by our very own Micheal Heap on what’s new and how we’ve listened to our customers’ needs.  #KongPin #Ingress #Kubernetes #K8s #GatewayAPI

2

Developer Experience is still a problem! I listened to this podcast https://lnkd.in/eZPvJnGE on how LastPass tries to make local experience much easier in the area of microservices. They went from the usual suspect of Docker compose but it requires you to build Docker images before being able to run things. Then they went to local kubernetes but it adds another layer and it doesn't help with the extra Docker build step. They decided to use nix which is Docker without Docker, universal package manager. This is something I looked at when working on codefly agents. One goal of codefly is to provide great Developer Experience, a developer starts any service, it will run any dependent services, do all the networking, and even provide hot-reloading for languages that don't have it (golang for example). I found nix to be too complicated so I am relying on Docker and spent quite some time getting that right: you really don't want to start/stop containers all the time and it's actually not that trivial to start and stop processes inside a Docker container. But the pain is worth it: - dependency is minimal, Docker is OK, nix is another story - performance hit is minimal since we try very hard to keep the containers around And agent can also use local stack if available. The philosophy of codefly is that your code needs some "co-pilot" for everything from setup, package maintenance, to networking, Docker build, kubernetes manifests. We do all the annoying stuff so you can just focus on writing code, writing tests that can depend on your full stack without any change of code, or mocking -- just that is a game changer and that's it. We take care of all the painful stuff so you can do the fun stuff!

1

Just read an amazing case study by Cloud Native Computing Foundation (CNCF) #cncf on how Seznam.cz opts #cilium to boost performance and reduce costs. This study highlights the pros of using cilium in the #Kubernetes Cluster. 🔴 Seznam is a Czech technology company that offers a variety of services including a search engine, news aggregator, TV streaming, email, and maps. 🟠 Challenge Faced by Seznam: - Costly F5 hardware Load balancer - Inefficient IPVS - High costs - Lack of automation, High CPU consumption 🟢 Solution: - Seznam selected Cilium for network, security and observability due to its high performance, open source nature and popularity - It's Kube-proxy replacement feature 🔵 Impact: - By numbers, HTTP requests grew to 1 million per second. - 100 + clusters can remain safely and effectively in a cluster mesh. - 100k + Endpoints are available across the DCs. - Cilium Layer 4 load balancer helped to save a lot of money for its CPU Usgae optimization Checkout the case study 👇: https://lnkd.in/gRf77Yfv

8

Hey! There's a great news for everyone interested in SRE / Platform / Security topics. We'll be hosting Docplanner Tech meetup in our Warsaw office, and this edition will be around those three areas. Also, during the meetup you'll have a chance to meet all team members of the Docplanner Platform (SREs, Platform Engineers, Platform Security Engineers, Software Engineers). --- "Reliability is the King" --- 🏗️ Building our own Internal Developer Platform - by Manuel Cañete 🔐 Vulnerability Management - Where to Start? - by Guillermo Palacio Oto 🚒 Fire defeated. What to do next? - by me Wednesday, May 22 at 6 PM in Warsaw Docplanner office (Kolejowa 5/7). Please, join the Meetup event and share with your friends interested in reliability. LINK IN THE COMMENT. Stay tuned!

40

1 komentář

🚀 Terraform Wars: The Great Naming & Modularization Debate 🤔 Terraform users, unite! Ever felt like Terraform is less about infrastructure and more about survival? Let’s dive into one of the biggest debates in the Terraform world: 🥊 One Module for All vs. Different Modules for Each Environment Team One-Module-to-Rule-Them-All: "Why write multiple modules when you can just use variables? Reusability is everything!" Oh sure, reusability is great—until you’re knee-deep in 30 variables and trying to figure out why is_this_even_working = true doesn’t fix your deploy. Team Separate-Modules-for-Everything: "Let’s split it up! More modules = more clarity, right?" Well, until you’re maintaining FOUR copies of the same thing and spending your weekends searching for that one missing tag across environments. Clarity? 🤷‍♂️ Where? And Then... Naming Conventions! 😱 Snake_case? kebab-case? Or how about YOLO_case? Naming AWS resources is like naming your Wi-Fi... It seemed funny at first, but now you're stuck with it forever. Pro tip: If your tags include prod-final-final2, you might need to rethink your life. 🙃 But Seriously… What’s the Answer? Spoiler alert: There’s no perfect answer. It’s all about trade-offs: ✅ A single module works great—until you need a PhD to manage all the conditionals. ✅ Separate modules feel clear—until you’re maintaining clones of the same code everywhere. Most teams start simple, with one reusable module. But as things grow (and let’s be real, they always do), you’ll need to rethink your strategy. Why Does This Matter? - Because Terraform is all fun and games until you inherit a setup named prod-backup-final-FIXED-FIXED2. 🤦‍♀️ And let’s not even talk about bloated modules that feel like mini-black holes. - Terraform isn’t just about managing infrastructure—it’s about keeping your sanity. 🧠 What’s Your Terraform Horror Story? Are you Team “One Module to Rule Them All,” or Team “Split ‘Em All Up”? How do you handle naming wars? 🤷‍♀️ Drop your thoughts (and your funniest naming fails) in the comments! Let’s laugh together—because if we don’t, we might just cry. 😂 📢 #Terraform #InfrastructureAsCode #DevOpsHumor #TerraformModules #NamingConventions #CloudComputing #AWS #DevOpsLife #IaC #TerraformTips #CloudInfrastructure #AWSCommunity #DevOpsEngineer #TechHumor #InfrastructureAutomation

1

🔍 OpenTofu vs. Terraform: Choosing the Right IaC Tool The Infrastructure as Code (IaC) landscape is evolving, and two names often come up: OpenTofu and Terraform. Both tools streamline infrastructure management, but understanding their differences can guide you to the right choice. 🌟 Terraform: - Mature and Robust: Backed by HashiCorp, Terraform is widely adopted, boasting a large community and extensive documentation. - Ecosystem and Support: Rich provider ecosystem and strong support make it ideal for enterprise environments. 🌟 OpenTofu: - Open Source and Flexible: As an open-source alternative, OpenTofu offers more flexibility with a focus on community-driven innovation. - Cost-Effective: Lower cost of entry, especially appealing for startups and small businesses. 🤔 Which to Choose? - Scale and Support: Opt for Terraform if you need enterprise-level support and a mature ecosystem. - Innovation and Cost: Choose OpenTofu for flexibility and budget-friendly options. Both tools are powerful; the best choice hinges on your specific needs and resources. 🚀 hashtag #IaC #DevOps #OpenTofu #Terraform #CloudComputing

3

Terraform Feature: Terraform Stacks are a feature intended to simplify infrastructure provisioning and management at scale, providing a built-in way to scale without complexity. There are a number of benefits to using small modules and workspaces to build a composable infrastructure. Splitting up your Terraform code into manageable pieces helps: Limit the blast radius of resource changes Reduce run time Separate management responsibilities across team boundaries Work around multi-step use cases such as provisioning a Kubernetes cluster Common use cases for Terraform Stacks Here are the common use cases for Stacks, out of the box: Deploy an entire application with components like networking, storage, and compute as a single unit without worrying about dependencies. A Stack configuration describes a full unit of infrastructure as code and can be handed to users who don’t have advanced Terraform experience, allowing them to easily stand up a complex infrastructure deployment with a single action. Deploy across multiple regions, availability zones, and cloud provider accounts without duplicating effort/code. Deployments in a Stack let you define multiple instances of the same configuration without needing to copy and paste configurations, or manage configurations separately. When a change is made to the Stack configuration, it can be rolled out across all, some, or none of the deployments in a Stack. Provision and manage Kubernetes workloads. Stacks streamline the provisioning and management of Kubernetes workloads by allowing customers to deploy Kubernetes in one single configuration instead of managing multiple, independent Terraform configurations. We see Kubernetes deployments that often have this challenge where there are too many unknown variables to properly complete a plan. With Stacks, customers can drive a faster time-to-market with Kubernetes deployments at scale without going through a layered approach that is hard to complete within Terraform. for more info: https://lnkd.in/gV5Fy4pF

13

2 komentáře

The guide to kubectl I never had. via Jake Page From the content: What kind of engineer are you? 🤔 Can somebody guess by just looking at you? More than likely not. Would that somebody be able to tell by looking at your keyboard instead? Might be a bit easier now. ⌨️ ...[Read more]

44

6 komentářů