Pablo Hinojosa Nava

Another great episode of The Edge, this time with Containerlab as the main topic and Roman Dodin as the guest! Many engineers already know that Containerlab is a fantastic tool for spinning up network labs quickly and lightweightly, thanks to its use of containers instead of VMs. Also, Containerlab makes it incredibly easy to share and reproduce labs. A Containerlab topology is basically just a handful of simple files, perfect for storing in a GitHub repository. But here’s something less well-known — I only learned it from this episode — and it deserves much more visibility. There��s one small action that dramatically improves the visibility and discoverability of any lab you publish: Add the clab-topo topic to your repository. Doing this makes your lab instantly discoverable under the clab-topo topic on GitHub. There are already 96 ready-to-use labs, and that number could skyrocket if more of us label our Containerlab repos with this topic. The beauty of it is that it takes only a few seconds!

44

3 Comments

Join us in welcoming the newest OpenInfra Foundation Platinum Member, Cachengo! Cachengo’s product roadmap outlines the strategic evolution of its infrastructure management solution into a robust platform powered by #OpenStack. The initial phase will emphasize the deployment of core OpenStack components, including Nova, Swift, Ironic and Neutron, with plans to evaluate additional services such as Keystone, Horizon and Cinder. In alignment with its adoption of OpenStack, Cachengo is also dedicated to actively contributing to the open source community, particularly through advancements in AI-driven applications. #opensource #AI #WeAreOpenInfra https://lnkd.in/g24MmuYB

31

1 Comment

𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 𝐲𝐨𝐮 𝐧𝐞𝐞𝐝 𝐭𝐨 𝐤𝐧𝐨𝐰 👀 1️⃣ 𝐌𝐨𝐝𝐮𝐥𝐚𝐫𝐢𝐭𝐲 – when writing code, make sure you follow the 𝐃𝐑𝐘 𝐩𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞 (don’t repeat yourself). Use modules for reusable code, so you don’t waste time setting up the same infrastructure multiple times. 2️⃣ 𝐕𝐚𝐫𝐢𝐚𝐛𝐥𝐞𝐬 – don’t hardcode values directly into your Terraform code. Use variables instead, so you can easily change values in one place without having to search through your files to update them. 3️⃣ 𝐂𝐫𝐞𝐝𝐞𝐧𝐭𝐢𝐚𝐥𝐬 – never hardcode sensitive information like your AWS access key or secret key. Use the 𝐞𝐱𝐩𝐨𝐫𝐭 command to store them in 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 𝐯𝐚𝐫𝐢𝐚𝐛𝐥𝐞𝐬 instead. This way, they won’t be exposed in the Terraform state file after you run terraform apply. 4️⃣ 𝐅𝐨𝐫𝐦𝐚𝐭𝐭𝐢𝐧𝐠 𝐚𝐧𝐝 𝐕𝐚𝐥𝐢𝐝𝐚𝐭𝐢𝐨𝐧 – run terraform fmt and terraform validate regularly. This keeps your code clean, consistent, and free of basic errors before applying changes. 5️⃣ 𝐍𝐚𝐦𝐢𝐧𝐠 𝐂𝐨𝐧𝐯𝐞𝐧𝐭𝐢𝐨𝐧𝐬 – use clear and consistent naming for resources, variables, and modules. This makes your code easier to read, understand, and maintain over time. 6️⃣ 𝐒𝐭𝐚𝐭𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 – always use a remote backend (like 𝐒𝟑 with 𝐃𝐲𝐧𝐚𝐦𝐨𝐃𝐁 for 𝐬𝐭𝐚𝐭𝐞 𝐥𝐨𝐜𝐤𝐢𝐧𝐠) to store your Terraform state file. This ensures your state is consistent, secure, and can be shared safely across your team. What other best practices would you include in this list? Leave it in the comments below 💬 #DevOps #Cloud #Terraform #TerraformBestPractices

19

Haven’t had the chance to explore the possibilities with the #MariaDB Enterprise Kubernetes Operator? Senior Software Engineer, Martín Montes Pérez, showcases this new, powerful solution by deploying a single MariaDB instance AND a multimaster 3-node Galera cluster with synchronous replication. 🧑‍💻 See the possibilities for yourself: https://bit.ly/402F7Jd 

24

1 Comment

Do you think about how to capture packets between your #Docker containers or from/to the outside? 🤔 I have received some questions about this, because i posted a screenshot. Since I'm a #NetworkNerd , i decided to create a short video on how to capture packets with #Edgeshark between my containerized Arista Networks cEOS switches deployed with Nokias #Containerlab. 📦 For this to happen, we use #Edgeshark for Web-Visualization, #Ghostwire for topology discovery, Packetflix to capture and as a Protocol Handler and #cshargextcap as an external capture plugin in #Wireshark . We could start packet capturing with a single click on the Wireshark icon next to the interface where we would like to capture. 🦈 #LookIntoYourContainers #RemoveBlindSpots #PCAPOrItDidntHappen Wireshark Foundation #Edgeshark #Docker Arista Networks Nokia 👇

13

3 Comments

#eoAPI Kubernetes v0.7.0 Release 🚀 🔗 https://lnkd.in/d5FnGYqs At Development Seed, we are excited to announce the release of #eoAPI Kubernetes v0.7.0, a major update that significantly improves the deployment flexibility and operational efficiency of Earth Observation APIs on Kubernetes. This release represents a substantial evolution in our infrastructure management approach, focusing on simplification, standardization, and enhanced user experience. 🌍 https://eoapi.dev/ The v0.7.0 release introduces a unified database deployment strategy, redesigned ingress system, modernized service architecture, and several new integrations that make the platform more adaptable to different deployment scenarios while maintaining robust operational standards. 1. Unified Database Architecture - Flexible PostgreSQL deployment supporting both integrated PGO operator and self-managed deployments - Enhanced PgSTAC bootstrap process using Helm hooks for reliable database initialization - Modernized database setup with cleaner, more efficient configuration - Streamlined database management and operations 2. Ingress System Improvements - New controller-agnostic ingress configuration that works seamlessly with both NGINX and Traefik - Streamlined path management and routing that reduces configuration complexity - Consistent behavior across different deployment environments 3. Service Architecture Enhancements - Refactored service-specific templates for better modularity and maintenance - Improved service organization and dependency management - Enhanced configuration flexibility and customization options 4. New Features - Integrated STAC Browser for intuitive data exploration and visualization - Azure Secret Vault integration enabling secure credential management - ArtifactHub.io integration for simplified package discovery and installation - Upgraded stac-fastapi-pgstac to v5.0.2 with latest STAC improvements This release marks a significant step forward in our mission to provide a robust, flexible, and user-friendly Kubernetes deployment solution for Earth Observation APIs. We encourage all users to upgrade to this version to benefit from these improvements and new features.

23

Not all SaaS secrets management platforms are built the same. This side-by-side comparison breaks down how on-prem vaults, traditional SaaS secrets platforms, and Akeyless zero-knowledge SaaS differ across architecture, key ownership, environment scope, cost, and compliance, so teams can understand where each model fits. Read the full article: https://hubs.li/Q03Z8JFY0 #secretsmanagement #cloudsecurity #identitysecurity

12

Managing secrets in #Kubernetes isn’t just about storage—it’s about visibility, control, and trust. In #SUSE’s latest #observability guide, learn how to securely create, manage, and monitor Secrets in your cluster—from TLS certificates to API tokens. 📦 What you’ll gain: ✅A breakdown of Kubernetes Secret types ✅Step-by-step creation and management tips ✅Observability insights to track and protect sensitive data Whether you're scaling cloud-native apps or tightening compliance, this guide helps you build secure foundations. https://okt.to/aGCYBj #KubernetesSecurity #CloudNativeOps #SUSE #DevSecOps #SecretsManagement #Observability #OpenSourceTrust

25

Terraform It is the team that arrives first on the site. They take care of everything structural: foundations, walls, main cables, central plumbing... In short, all the basic infrastructure on which the rest will be based. Ansible With Terraform what you could create: Network: Define a VPC, public/private subnets, firewall rules. Machines: Deploy EC2 instances (AWS), VMs (Azure/ GCP), or even Kubernetes clusters. Storage: Create S3 (AWS) buckets, persistent disks. Databases: Provision an RDS (AWS) or CloudSQL (GCP) database. Load balancer: Implement a load balancer to distribute traffic. He arrives once the building is standing. This is the layout and customization team: applying the paint, installing the furniture, configuring the lighting, placing the decorations... Everything that makes the space livable and adapted to your needs. With Ansible what you could do on it: Configure the system: install packages (nginx, docker, git...), manage users, set rights. Deploy an app: clone a Git repository and launch your app. Configure services: for example, set up Nginx to serve a site, or PostgreSQL with users and databases. Security: apply local firewall rules (ufw/iptables), strengthen SSH configuration. Automation: restart services, manage conf files, apply Jinja2 templates.

18

We shipped two updates this month to make it easier to build and manage with Pinecone: Database: ‣ We released Terraform Provider v2.0.0, adding support for managing API keys and projects. This makes it easier to keep Pinecone resources in sync with the rest of your infrastructure. Assistant: ‣ Assistants can now gather context directly from images in PDFs— extending multimodal support beyond text. This feature is in public preview, and you can try it today in the docs. Full details → https://lnkd.in/gB_4hjiU

14

1 Comment

Multi-cluster Kubernetes shouldn’t feel like a never-ending maze of clusteradm commands and Helm charts. That’s why we contributed the fleetconfig-controller to the Open Cluster Management (OCM) community. It turns what used to be a tangle of imperative steps into a clean, declarative workflow that’s GitOps-ready and aligned with Kubernetes best practices. In this blog, you’ll see how it simplifies OCM orchestration by: 🔸 Automating hub and spoke cluster lifecycle management 🔸 Supporting OCM add-ons across managed clusters 🔸 Enabling GitOps for multi-cluster topologies 🔸 Reducing complexity in bootstrapping and maintenance The result: an easier, more consistent way to manage OCM multi-clusters at scale. Read the full blog here 👉 https://okt.to/w72mOU #Kubernetes #KubernetesManagement #CloudNative #DevOps

8

⚡️ Kubernetes keeps your infrastructure alive. Temporal keeps your application logic alive. Together, they make your system resilient. But standard K8s configurations often aren’t optimized for Temporal workloads. In our latest guide, we cover the essential patterns for production success, including: - Helm charts: configuring for production vs. development. - Autoscaling: why CPU metrics mislead and how to use KEDA instead. - Performance: tuning GOMAXPROCS to prevent latency issues. Read the new blog post by Gapilan (Cubby) Sivasithamparam: https://lnkd.in/gHfeJnth

45

1 Comment