Lampros Batalas

DevOps guy has to do Code Reviews and Integration and e2e Tests writing too. Because that is the only way to ensure: * Produced micro services are in high quality * Security against the hackers No automatic filters will magically help here. One super skilled programmer has to look at the fingers of less experienced colleagues. He has to be subordinate just to CEO, not CTO. Independence, protection from retaliation. Ability to deny backend updates, and there must be nothing the Programmers can do then. Lazy Programmers with attitude problems must be monitored even more. Even if "the team decided" to not do this or that, someone has to protect the company and do not let sloppy work through. Sometimes the hacker infiltrates the company, and attacks from the inside. Then such control is even more important. Many DevOps Pipelines idea is just like that, and that is what the managers often are asking for. They need Programmers to do professional high quality work. And the Programmers do not do that. How to achieve this level of control? #devops #programming #softwaredevelopment

2

1 Kommentar

https://lnkd.in/dPkaMbbe << ...Agile is not about the absence of architecture but is focused on the feedback process: planning but having immediate feedback... >> #randomthought rich of ideas and starting point to going in deep... note: microservice is more about deploy, agile is more about feedback, evolutionary architectures do not exist... in short, we return to the classic One Size Fit All is a mistake! ;-)

2

DDD this-and-that is all over my feed. Why? Why now? Is this hype? A web search on DDD produces lots to read. The concept is fully enabled by its own hype machine - consultants, books, conferences, advocates, etc. So ... it's a thing. Then I came across an article[1] that testified: ⭐ The strategic design of DDD gives us options for the future without knowing what the future will look like. ⭐ The tactical patterns give us strong weapons against continuously deteriorating software. Hmmmm. Those are yummy rewards!! - let's jump in bit more .... <wern> <reading amount='lots' /> </wern> Oof. So much jargon ... If I simplify, I see 3 main concepts: 1. Everyone (business, product, engineering, customers) needs to talk the same language. Get everyone on same page about the desired outcome, challenges and options. 2. Break complex problems into manageable pieces. The pieces should align with how the organization is divided Smaller, more understandable sections. Each section with clear boundaries and its own specific purpose. Then each domain becomes easier to understand, build, and change without disrupting the entire system. 3. Focus on the "real-world" problem Most software development gets lost in technical details. DDD *first* forces a deep understanding of the actual business problem. The idea is to turn software from being a technical artifact to a (jargon alert) living representation of a business's real-world operations. I'm in ... But want to note that it mostly seems like common sense to me !? Developers have long talked like this: Use good naming + Separation of concerns + Get good requirements about What (not How). Disagree? Did I miss the point? Is DDD hype?

1

API Gateway + Kubernetes 🤝. Kong Inc. Champion and Chief Integration Evangelist / Chief Architect at OPITZ CONSULTING Deutschland GmbH, Sven Bernhardt on how to secure APIs with plugins in your Kubernetes management.  Full blog + video here covering:  - 🛠️ Installing Kong Ingress Controller - 🔐 Securing APIs with plugins - 📡 Exposing Kubernetes services as APIs, securing APIs with plugins (authentication, rate-limiting) - 🌐 Using the Gateway API for HTTP/TCP routing - 📊Observing analytics - all managed via the centralized Kong Konnect control plane. #KongPin #Kubernetes #Ingress #K8s #LearnToCode

1

🔭 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 Kommentare

Alex Kretzschmar, also known as ironicbadger, has posted an insightful YouTube Video on how to get started with #Docker and #Tailscale. This video is perfect for those looking to enhance their #DevOps skills and secure their network connections. In his insightful video, Alex Kretzschmar (aka ironicbadger) walks viewers through the process of setting up Docker with Tailscale. This combination allows for easy, #secure access to Docker containers across various environments. Alex covers the basics of Docker containerization and how Tailscale's mesh #VPN simplifies secure connectivity. His step-by-step guide ensures that even beginners can follow along and implement these tools efficiently. For more details, check out the full guide on the Tailscale blog. Blog post: https://lnkd.in/gwCTAsAK

1

DevOps Life Hacks - 51 If you work with CLI a lot, set up an Alias. It makes workflow easy and fast. You don’t have to remember long commands. You can add those in the executable file depending on the type of terminal you are using. For zsh - .zshrc (Mac) For bash - .bashrc (Linux) Add these to your shell configuration file (.bashrc, .zshrc, etc.) to make them persistent. Simplify your command line experience and work more efficiently! https://lnkd.in/gJJKCxyV Check out my alias: https://lnkd.in/gXc4btpr #ShellScripting #Productivity #DevOps #CommandLine #Automation #TechTips #DevOpsLifeHacks

17

4 Kommentare

DORA's yearly "State of DevOps Report" is out and it should consider and apply some kind of "inflation reduction act" for page count. 120 pages, yes, 120 pages. Okay, there are a lot of pictures (like in good old uni times), but still 120 pages. The only significant reduction in page count was in 2020 when they switched to a different format. About the report: yes high-performing teams are doing better than low-performing teams. And AI will make everything better #DORA #State-of-DevOps #humour

16

2 Kommentare

🌍 The World of Containerization with Poda James 🌐 Cloud Infrastructure & Linux System Administrator 🛠️ Lets take it from top what is DOCKER? Alright, think of Docker as your "magical moving box" for apps. 🚀 Magic Moving Box: Docker is like a magic box that packs up your app so it can travel smoothly. 🧩 App Kit: It includes every piece your app needs—libraries, settings, the works. 📦 Container: The box, or container, keeps it all tidy. 💻 Runs Anywhere: Your app can go from laptop to server (even spaceship!). 🎉 No More Drama: No “works on my machine” excuses, just smooth sailing anywhere your app goes! Let me give an example with your favorite Application on your phone >> mmm lets take Spotify for example. Think of Docker like your favorite app, Spotify 🎶. When you use Spotify, it streams music from its servers, but the app itself contains everything you need to enjoy your music—playlists, settings, and your favorite tracks. Docker does the same for software applications: it packages everything an app needs to run (like libraries and configurations) into a "container." This way, no matter where you run the container—your laptop, a server, or even in the cloud—it works the same way, just like Spotify works on any device! Now lets talk about why docker is important how its used on your favorite application! To illustrate how Docker helps run an application like Spotify, here’s a simplified breakdown: User Interface 🖥️: When you open the Spotify app, you interact with the user interface, which is served by a Web Server Container. Application Logic 🎵: The app's logic, such as searching for songs or managing playlists, runs in an Application Container. Database 📊: User data and music catalogs are stored in a Database Container, which handles all data transactions. Communication 🔗: These containers communicate over a Docker Network, ensuring smooth interaction and data flow. Scaling 📈: As more users join, Docker can quickly spin up additional containers to manage the load, maintaining performance and reliability. Lets talk about the technical aspect of docker the next post. Happy reading!! Happy weekend!!

4

🚀 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

It definitely takes more than 40 hours, much more. Sometimes, persistence is not possible because some People overwrite Roots SSH private keys. It's unfortunate that multiple people can access the same machines simultaneously. As a tip, be sure to create a write-up for all machines it will safe you a lot of time. #HTB #OffShore #ProLabs

6

Indeed S3 can be used as a container registry - it has versions, deletion protection and etc. The only thing I think is missing is a built-in security scan.

2

In Kubernetes we know that with, kind: Pod we can only create a pod and if it is deleted I can't be created again. That's why another object came. Kind: Deployment with the deployment object we came to know that we can achieve Auto - healing, Auto - Scaling and Enterprise level application support. But here the twist is Auto - Scaling cannot be achieved alone with the Deployment object. It will directly depend upon the Horizontal pod AutoScaling and ResourceQuota. Deployment will also do some other things. But I want to highlight this. 𝐇o𝐩e t𝐡i𝐬 𝐢s u𝐬e𝐟u𝐥. A r𝐞p𝐨s𝐭 𝐡e𝐥p𝐬 𝐞v𝐞r𝐲o𝐧e. 𝐀p𝐩r𝐞c𝐢a𝐭e a c𝐨n𝐧e𝐜t𝐢o𝐧 𝐨r a f𝐨l𝐥o𝐰 𝐀y𝐮b s𝐡a𝐢k 𝐈 𝐰i𝐥l e𝐱p𝐥a𝐢n t𝐡e D𝐞v𝐎p𝐬 𝐫e𝐥a𝐭e𝐝 𝐭h𝐢n𝐠s i𝐧 𝐞a𝐬y a𝐧d u𝐧d𝐞r𝐬t𝐚n𝐝a𝐛l𝐞 𝐰a𝐲. 𝐀n𝐝 𝐭h𝐚n𝐤 𝐲o𝐮 𝐫e𝐚d𝐢n𝐠 𝐦y d𝐞a𝐫 𝐟r𝐢e𝐧d 😊

4

Chatgpt is becoming more of a great everyday tool in an IT person's toolbox. The more you understand it and understand how to extract the information you need out of it, its easy to skip pass the fluff or things that dont make sense. Needing to import hundreds of existing subnets into terraform using terraforms import block, i knew i did not want to import all of that per subnet and that i also needed to import these into modules. Essentially I have a code block that does a for_each through all of the subnets that come into the variable. import {  for_each = { for key, value in var.subnet : key => value if value.import }  id = each.value.import_resource_id  to = module.subnet.azurerm_subnet.main[each.key] } Only problem was i needed all of those subnets in a specific format in my tfvars file before i could do that. In comes chatgpt and a very much needed python script. As somebody who didnt have the need or time to spend a ton of time writing that script out, i was able to ask it a very small subset of questions piecing this script together found here in my github https://lnkd.in/gWSarEpH. I of course used powershell to export out the subnets in a specific format also that was needed. All in i was able to take a task that could have taken me days to complete by not having to manually import all those subnets in one by one and also generating a script using chatgpt vs having to search forums and ask around and get a bunch of methods for the same outcome. What are some IT use cases you have used chatgpt to improve daily task? #chatgpt #ai #automation #scripting

5

1 Kommentar

Dear software developers, Small recap about #ELF (it has nothing to do with german national soccer team) ELF as unix-like system specific executable contains additional, metadata information that can be used to inspect the by the compiler generated file. These information are stored into different kind of sections: - Header: describes the executable in terms of the type of the executable, architecture, and other attributes - Program headers: these describe the runtime properties of each segment, like code, data, stack, etc. - Section headers: these describe each section within the binary, like symbol tables, string tables, and similar - Symbol tables: unless the binary is stripped (‚strip <executable>‘) - as usually is for building the release binary, the ELF contains symbol tables and therefore information that can be used for core dump analysis (f.e. with gdb), about the function and variables, their names and addresses, everything that is required to retrieve some meaningful backtraces - Dynamic link information: about the external - shared library dependencies This way you can use a different kind of tools, like objdump (,objdump -x <executbale>‘) to inspect the binary on all these metadata information, or even disassemble machine code to human-readable assemble code (,objdump -d <executable>’). Another useful tool that can leverage on these descriptive information included in ELF is ldd - to inspect the dynamic link information: (,ldd <executable>’). This could be useful to resolve the issue when some shared libraries are missing on the target - are not deployed, which prevent executable to run, especially if this binary is not originally part of the image (f.e. if you want to use tcpmdump diagnostic tool that is not by default delivered with the image). # For more content, please visit my blog https://lnkd.in/dMPi7cvg Feedback as usual more than welcome. #unix #embedded #cplusplus #programming

18

4 Kommentare

Container images used to build you software to ship to Kubernetes cluster in cloud with minimal setup and 0 CVE's is a real challenge and not the only one of your CI/CD pipeline. Interesting approach of https://lnkd.in/dbiizSq5

9

🚀 Terraform Tip: Leveraging Validation Blocks 🚀 Did you know Terraform now supports validation blocks in modules and variables? This feature allows you to enforce custom rules on input variables, helping catch configuration errors early. 🔑 Why Use Validation Blocks? Error Prevention: Ensure inputs meet specific conditions before deployment. Improved Readability: Clearly define and document constraints within your code. Stronger Modules: Create more robust, reusable modules by enforcing required patterns or value ranges. If you're not using validation blocks yet, it's time to start making your Terraform configurations more reliable! 🛠️ #Terraform #InfrastructureAsCode #DevOps #CloudInfrastructure

1