Sebastian Fyda

Tech and space industries are moving faster than light (well, almost), and the demand for game-changing talent has never been greater. Whether it’s DevOps experts optimizing the backbone of innovation, cybersecurity specialists keeping the bad guys at bay, or space ops pioneers enabling groundbreaking missions, these roles are shaping the future. This is where myself and EVONA step in. We don’t just recruit - we connect visionaries with opportunities that matter. Our mission? To help companies build elite teams while empowering talent to land their dream roles. Why partner with us? Because we don’t do “one-size-fits-all.” We take the time to truly understand your needs, whether you’re hiring or job hunting. Think of us as your career matchmakers, but with a tech and space twist. 2025 is the year to make big moves. So, if you’re ready to collaborate, innovate, and dominate, let’s talk. Your dream team, or dream job - is just a message away. #devops #cybersecurity #space #aerospace #defense #deeptech #innovation #hiring

10

Something happens in the dark (with lovely magenta background light :) )... Homelab and my sandbox system in action again. Main focus on compiling postgres and pgbackrest together from source and build a wide usable, well-featured rpm/deb package for ansible-automation purposes. Deploy them with a playbook and setup the whole environment. New challenge again but I see the light at the end of the tunnel now. Love this solution. #ansible #automation #lovemyjob #postgres #pgbackrest

22

6 Comments

🌍 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

🔭 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

6 Comments

⚙ Using S3 as a container registry is 5-8 times faster than ECR! Very interesting approach by Adolfo Ochagavía. Definitely worth a look. #aws #awscommunity #awscommunitybuilders #devops https://lnkd.in/dHAQz2EN

1,386

104 Comments

Next Monday, May 13th I will be joining the Nürnberg AWS User Group to talk about scaling in EKS efficiently and in response to the right metrics 😁 We will be checking two of the hottest Kubernetes projects: KEDA and Karpenter, and discussing how to fine-tune them for production-grade environments. https://lnkd.in/d4uZkREX #aws #communitybuilder #eks #kubernetes #efficiency #finops

53

4 Comments

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 Comment

What is Terraform? How does it work? (and why the name is so good) 3 people who asked me what Terraform last Thursday. And that was at SREday AMS, full of SREs and DevOps. I was shocked, I thought everyone was already using it. But perhaps it needs a refresher, so here TL;DR (I started drawing a diagram, but then found this beautifully animated one from Nikki Siapno) 1. Infrastructure as Code (IaC) ↳ IaC is not a complicated concept ↳ check in the infrastructure config to version control ↳ leverage the same tooling (git, PRs, linting) ↳ fairly uncontroversial 2. Terraform ↳ de-facto standard for IaS ↳ the first product to reach mainstream adoption ↳ open-source, backed by HashiCorp ↳ before HashiCorp got that bad rep ↳ coincides with massive Cloud adoption 3. How does Terraform work? ↳ write your infra config in a file (~vim file.tf) ↳ run terraform plan to see what it will do (~git diff) ↳ run terraform apply to create the infra (~git commit) ↳ do something with the state file (~git push) 4. The state file? ↳ it holds a bunch of data like ids, relationships, etc ↳ TF uses it to know what artifacts it owns ↳ can be stored remotely, like S3 bucket ↳ you're in trouble when it gets messed up 5. Why Terraform? ↳ other options include Pulumi and maybe Ansible ↳ wide range of modules to do almost anything ↳ popular - easy to google problems ↳ plenty of docs, tutorials etc So here it goes. IMO it's no longer a nice-to-have, it's a requirement for any modern stack. Oh yeah, and the name is great. It means exactly what it does, and unlike for example Go (everytime you google, you have to use Golang) it's actually super easy to google things. Are you using Terraform? Let me know below. And follow me Miko Pawlikowski 🎙️ if you like this kind of stuff.

59

46 Comments

A few weeks ago I hinted that I am writing course for the Terraform Associate certification that I will publish on Leanpub. I've seen a few people who have entered interest in this course already (you can express interest here https://lnkd.in/dDiK7-Kq) 🧑‍🎓 👩‍🎓 The course is progressing and is about 30%-40% done. I am learning a lot about how to create courses! At first I was sure I knew the difference between a quiz and an exercise. Then I realized they are basically the same thing, except with some major differences. The current state of affairs is that each lesson will have one or more collections of exercises, and the whole course will end with a number of quizzes. Each quiz will resemble the actual exam (as far as the Leanpub platform allows). #terraform #certification #course #author

15

How can we distinguish AWS Amplify from AppSync? 🤸​ While talking about AppSync on Community Day Poland, I noticed people need clarification about these excellent services and their purposes. Even though they are both related to GraphQL, they serve different purposes. Let's discuss several features of both. 💻​ Amplify is a multi-purpose service whose main element is CLI. It can connect the API, front end, storage, and authentication. The user can use traditional REST with API Gateway or AppSync with GraphQL. The latter service is also having similar capabilities but without front-end and CLI. 🏆 Amplify focuses on developer productivity, which means that the engineer can achieve the goal of delivering features faster. AppSync will provide different services because one must choose the IaC tool, which could now be CDK, Terraform, Pulumi, or something totally different. Amplify is a more opinionated way of building applications because it enforces specific folder structures, for example, with specific tools to use. ​🌎​ Furthermore, the naming of the services gives a hint. Amplify is about increasing or enlarging the experience, while AppSync is more about coordinating the parts. Both services are good at what they can do, but Amplify is more potent with the lock-to-specific way of building apps. Please let me know if you have experience using Amplify and AppSync in the comments. #aws #devops #cloud #awscommunity #sorokatech

5

3 Comments

Kubernetes is evolving, the CKA exam too! https://lnkd.in/dwcMpyfE "Here are 2 examples of changes: Removal of the competency “Provision underlying infrastructure to deploy a Kubernetes cluster” because since the last update that happened a couple of years ago Kubernetes usage reality is now in a managed platform. Introduction of a competency related to Gateway API: “Use the Gateway API to manage Ingress traffic” "

4

What should you consider when using Amazon RDS with AWS Lambda? Check out a new blog article by our Arttu Pekkarinen!

5

𝙄𝙨 𝘿𝙚𝙫𝙊𝙥𝙨 𝙗𝙪𝙧𝙣𝙤𝙪𝙩 𝙖𝙘𝙩𝙪𝙖𝙡𝙡𝙮 𝙖 𝙩𝙝𝙞𝙣𝙜? 😵   Are we in the middle of the Great DevOps Burnout? A report from Haystack suggests - 𝙔𝙀𝙎.   83% of the 258 software engineers surveyed reported feelings of burnout from high workloads, inefficient processes, and unclear goals and targets. 74% of software engineers surveyed reported working on operations tasks in some capacity.   Another survey from Spacelift follows a similar theme (𝘒𝘌𝘠 𝘍𝘐𝘕𝘋𝘐𝘕𝘎𝘚 𝘚𝘏𝘖𝘞𝘕 𝘍𝘙𝘖𝘔 𝘛𝘏𝘐𝘚 𝘚𝘛𝘜𝘋𝘠🔎).   They found that “DevOps engineers are more frequently stressed than the IT average. Over 40% admit to being stressed ‘often’ or ‘very often’ compared to 34% of the IT average.” The study suggests that DevOps are the most stressed because they feel their skills are insufficient for their jobs.   Are their skills insufficient or does their setup lack a platform that provides sufficient support❓   In other words, it seems that a lot of folks “doing DevOps” are also burnt out. I think we have more research to do before we pinpoint the exact causes of this stress. But I don’t think the trend is a coincidence.   There is a growing conversation in the DevOps community about whether developers can or want to take on operations tasks. The main problem they’re encountering is cognitive load, which prevents developers from focusing on developing features and delivering the most value to the company. The organisation’s efficiency suffers as a result, and likely the developers’ well-being too.   Are you feeling the “Great DevOps Burnout”❓ If not, what is your organisation doing well❓ Cubiq Recruitment | #devops #platform #developer #burnout

24

1 Comment

First, I have an doubt how these containers, pods and services will communicate with each other and later this communication is called as "Kubernetes Networking". when I am preparing kubernetes I did not notice that much about kube proxy and CNI pluggin. But, later on I came to know that without these two communication is impossible. communication between containers in pod: containers use pod IP for external communication and for internal communication it uses local host and the port that container exposes. communication between two pods in same node: CNI plugged establishes the bridge network and this is connected to the multiple network of the pods in the same pod. so each pod will have a virtual ethernet interphase. so when pod A wants to communicate with pod B. pod A creates a packet with destination IP address and sends it to the virtual ethernet interphase of pod A, as both pods network interface is connected to the bridge network. the packet will travel through the bridge network to the virtual ethernet interphase of pod B. from here packet will travel to pod B and this packet will be processed by pod B and communication is established.

1

Podman is a powerful alternative to Docker, especially for users looking for a daemonless and more secure container management tool and also a light weight tool. Podman is an open-source tool designed to manage containers and pods (groups of containers) without requiring a daemon, which makes it different from Docker. Here are a few key features of Podman: 1.Daemonless Architecture: Unlike Docker, which relies on a central daemon, Podman runs containers in a daemonless architecture. This means it can run containers under the user account, providing a more secure and lightweight experience. 2.Compatibility with Docker: Podman can use Docker containers and Dockerfiles, making it relatively easy to switch from Docker to Podman. It provides a Docker-compatible command-line interface (CLI), allowing users to run commands like podman run instead of docker run. 3.Rootless Containers: Podman supports running containers as non-root users, enhancing security by reducing the attack surface.Kubernetes Integration: Podman can generate Kubernetes YAML files from containers, facilitating the transition from container development to Kubernetes deployment. 4.Pod Support: Similar to Kubernetes, Podman supports the concept of pods, which are groups of containers that share the same network namespace, making it easier to manage multi-container applications. For example, to run a container with Podman, you can use a command similar to Docker. podman run -d --name my-container nginx

2

2 Comments

First of my publications after re:Invent. I share my quick insights about the announcements and the whole conference. More will come :) https://lnkd.in/dqq-mTxN Please like, comment and subscribe, help me to grow my audience! #awsreinvent #cloud #aws

6

I love reading this kind of story: https://lnkd.in/d5kW_WcW Not because I don't like k8s, but because it's just common sense! Kubernestes is certainly a great technology, but it's overly complicated for many companies, and also not needed in most cases: ✅ Use the right tools for the job. ✅ Use managed services. ✅ Start simple and grow/evolve when required (Lambda➡️ Fargate ➡️ ECS ➡️ EKS) It's complex to do simple, especially in this world where buzzwords and the gaze of others tend to dictate our architecture choices. Kubernestes looks good in a resume for sure, but when you're spending your nights and weekends on-call, not sure it's worth the pain.

177

30 Comments