KevisAlex’s “Interpreting Terraform Plan Outputs with the Help of an LLM” demystifies how large language models can translate Terraform’s complex plan data into practical insights. This blogpost guides DevOps teams through clear, step-by-step examples to streamline infrastructure as code workflows.
https://medium.com/@KevsAlex/interpreting-terraform-plan-outputs-with-the-help-of-an-llm-8f9824c63ecd
https://medium.com/@KevsAlex/interpreting-terraform-plan-outputs-with-the-help-of-an-llm-8f9824c63ecd
Medium
Interpreting Terraform Plan Outputs with the Help of an LLM
So, you’ve got a Terraform plan output in front of you. It’s filled with lines of code that look like a language only your computer…
❤1👍1
Recently, I received a message from a recruiter about an open position. We chatted, I sent my CV, and after a week they asked about my desired salary. Then they set a time to sign an NDA before any interview. That was my first warning sign.
I read the NDA carefully and found a few red flags worth sharing (my personal view, not legal advice):
Very broad definition of “Confidential Information.”
The NDA says “Confidential Information” means “any and all information…in whatever form,” including “business plans, forecasts, projections, analyses, compilations, records and other materials” . This could cover even simple chat notes - so you might break the agreement just by asking a normal question.
Three‑year term.
The NDA stays in force for three years from signing . For a one‑time interview, this long period seems too much. It could stop you from working on similar projects elsewhere for a long time.
Foreign jurisdiction.
All disputes must go to the DIFC Courts in Dubai under DIFC law . If you disagree, you could face high travel and legal costs to defend yourself there.
No warranties on information.
The NDA states there are no promises about the accuracy or completeness of the shared information . Yet if you accidentally misuse something, you are fully responsible.
Surprise timing of the NDA.
The recruiter never mentioned the NDA at the start. It only appeared at a late stage - after salary discussions and interview timing agreement. That “tricky” timing feels like a hidden catch.
Always read an NDA line by line. Ask:
- “What exactly counts as confidential?”
- “Why is the term so long?”
- “Am I okay with this jurisdiction?”
A few clear questions now can save you big headaches later.
Have you ever reviewed an NDA with similar points? What questions did you ask before signing?
I read the NDA carefully and found a few red flags worth sharing (my personal view, not legal advice):
Very broad definition of “Confidential Information.”
The NDA says “Confidential Information” means “any and all information…in whatever form,” including “business plans, forecasts, projections, analyses, compilations, records and other materials” . This could cover even simple chat notes - so you might break the agreement just by asking a normal question.
Three‑year term.
The NDA stays in force for three years from signing . For a one‑time interview, this long period seems too much. It could stop you from working on similar projects elsewhere for a long time.
Foreign jurisdiction.
All disputes must go to the DIFC Courts in Dubai under DIFC law . If you disagree, you could face high travel and legal costs to defend yourself there.
No warranties on information.
The NDA states there are no promises about the accuracy or completeness of the shared information . Yet if you accidentally misuse something, you are fully responsible.
Surprise timing of the NDA.
The recruiter never mentioned the NDA at the start. It only appeared at a late stage - after salary discussions and interview timing agreement. That “tricky” timing feels like a hidden catch.
Always read an NDA line by line. Ask:
- “What exactly counts as confidential?”
- “Why is the term so long?”
- “Am I okay with this jurisdiction?”
A few clear questions now can save you big headaches later.
Have you ever reviewed an NDA with similar points? What questions did you ask before signing?
😱11🔥3👍2🤯2❤1
AWS Senior Solution Architect Specialist Sébastien Allamand outlines how Amazon VPC Lattice combined with EKS Pod Identity IAM session tags enables secure communication across multiple Kubernetes clusters. This post demonstrates encryption in transit, fine-grained attribute-based access control, and Envoy sidecar proxies to simplify cross-cluster connectivity.
https://aws.amazon.com/blogs/containers/secure-cross-cluster-communication-in-eks-with-vpc-lattice-and-pod-identity-iam-session-tags/
https://aws.amazon.com/blogs/containers/secure-cross-cluster-communication-in-eks-with-vpc-lattice-and-pod-identity-iam-session-tags/
Amazon
Secure Cross-Cluster Communication in EKS with VPC Lattice and Pod Identity IAM Session Tags | Amazon Web Services
This blog was authored by Sébastien Allamand (Sr. Solution Architect Specialist, Containers). This blog has also been translated into Portuguese here. Solution overview When you create your applications and want to expose internal API endpoints, you can build…
👍1
In “Using Go Instead of Bash for Scripts,” Krzysztof Kowalczyk showcases how Go programs can supplant traditional shell noscripts for running, testing, and deploying applications. This tutorial outlines a single multi-purpose Go command-line tool with flags and helper functions for process execution, file handling, and environment management.
https://blog.kowalczyk.info/article/4b1f9201181340099b698246857ea98d/using-go-instead-of-bash-for-noscripts.html
https://blog.kowalczyk.info/article/4b1f9201181340099b698246857ea98d/using-go-instead-of-bash-for-noscripts.html
blog.kowalczyk.info
Using Go instead of bash for noscripts
❤3
This article explains how AWS’s open-source Bottlerocket OS strips away unnecessary components to provide a lean, secure foundation for running containers at scale. It highlights integration benefits with services like EKS and lays out performance, security, and operational gains for cluster operators.
https://aws.amazon.com/blogs/containers/benefiting-from-bottlerocket-an-open-source-container-optimized-operating-system/
https://aws.amazon.com/blogs/containers/benefiting-from-bottlerocket-an-open-source-container-optimized-operating-system/
Amazon
Unlocking Benefits with Bottlerocket: A Purpose-Built Container OS | Amazon Web Services
Post updated on Nov 26, 2024. This post discusses Bottlerocket, a Linux-based open source operating system that is purpose-built for running containers. We will walk through fleet management at scale and how users can benefit from it. We will also share the…
❤5
In this blogpost the AWS Containers team walks through a real-world scenario, showing how to streamline container deployment pipelines using native AWS tooling and best practices. Readers gain practical guidance on automating builds, scaling workloads, and monitoring production clusters with minimal overhead.
https://aws.amazon.com/blogs/containers/16532-2/
https://aws.amazon.com/blogs/containers/16532-2/
Amazon
How to Run WebAssembly on Amazon EKS | Amazon Web Services
WebAssembly (Wasm) is a revolutionary technology that promises to bring near-native performance to web applications. However, its potential extends far beyond the browser, enabling developers to run Wasm workloads in various environments, such as cloud-native…
Effortlessly visualize mod graph with all external dependencies for your Go projects
https://github.com/bayraktugrul/modview
https://github.com/bayraktugrul/modview
GitHub
GitHub - bayraktugrul/modview: Effortlessly visualize mod graph with all external dependencies for your Go projects
Effortlessly visualize mod graph with all external dependencies for your Go projects - bayraktugrul/modview
👍3
The write-up by Overcast explores whether Kubernetes pods are truly evicted because of CPU pressure or if other scheduler nuances are at play. By dissecting eviction events and kubelet metrics, the author equips operators with actionable tips to diagnose and prevent unexpected pod terminations.
https://overcast.blog/do-pods-really-get-evicted-due-to-cpu-pressure-2b27274a670c
https://overcast.blog/do-pods-really-get-evicted-due-to-cpu-pressure-2b27274a670c
Medium
Do Kubernetes Pods Really Get Evicted Due to CPU Pressure?
As Kubernetes administrators and developers, we’ve all heard the notion that pods can get evicted due to high CPU pressure on a node. But…
👍4
This piece argues that GitHub’s network effects, developer experience, and strategic acquisitions ultimately cemented its dominance in the code-hosting world. It contrasts competing platforms and offers lessons for toolmakers seeking to build thriving ecosystems.
https://blog.gitbutler.com/why-github-actually-won/
https://blog.gitbutler.com/why-github-actually-won/
Butler's Log
Why GitHub Actually Won
How GitHub _actually_ became the dominant force it is today, from one of it's cofounders.
❤1🔥1
Laminar - open-source all-in-one platform for engineering AI products. Create data flywheel for your AI app. Traces, Evals, Datasets, Labels. YC S24.
https://github.com/lmnr-ai/lmnr
https://github.com/lmnr-ai/lmnr
GitHub
GitHub - lmnr-ai/lmnr: Laminar - open-source all-in-one platform for engineering AI products. Create data flywheel for your AI…
Laminar - open-source all-in-one platform for engineering AI products. Create data flywheel for your AI app. Traces, Evals, Datasets, Labels. YC S24. - lmnr-ai/lmnr
👍4❤1
vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
https://github.com/loft-sh/vcluster?tab=readme-ov-file
https://github.com/loft-sh/vcluster?tab=readme-ov-file
GitHub
GitHub - loft-sh/vcluster: vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace…
vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters...
👌3
The post from Massdriver demonstrates how to generate clean Infrastructure-as-Code configurations from resources that already exist in your cloud accounts. Through step-by-step examples, it shows teams how to regain version control and security compliance without rebuilding everything from scratch.
https://www.massdriver.cloud/blogs/generating-infrastructure-as-code-from-existing-cloud-resources
https://www.massdriver.cloud/blogs/generating-infrastructure-as-code-from-existing-cloud-resources
Generating Infrastructure-as-Code From Existing Cloud Resources | Massdriver Blog
Generating Infrastructure-as-Code From Existing Cloud Resources
Generating OpenTofu or Terraform from existing cloud resources is a tedious process fraught with gotchas. It's not a silver bullet for click-ops debt. This post will discuss caveats of tools and different approaches to generating IaC.
1
In his overview, Martin Heinz unpacks a recent technical challenge and walks readers through the solution, complete with code snippets and performance benchmarks. The candid narrative emphasizes practical learning and encourages experimentation in everyday development workflows.
https://martinheinz.dev/blog/111
https://martinheinz.dev/blog/111
martinheinz.dev
Recent Docker BuildKit Features You're Missing Out On
<p>
With introduction of BuildKit - the improved builder backend for Docker - many new features has been added to Docker, many of which are little known. S...
With introduction of BuildKit - the improved builder backend for Docker - many new features has been added to Docker, many of which are little known. S...
Real-time monitoring of Linux process network traffic, including the client IP, port, and transfer speed for each connection.
https://github.com/CDWEN0526/tmd-top
https://github.com/CDWEN0526/tmd-top
GitHub
GitHub - CDWEN0526/tmd-top: Real-time monitoring of Linux process network traffic, including the client IP, port, and transfer…
Real-time monitoring of Linux process network traffic, including the client IP, port, and transfer speed for each connection. - GitHub - CDWEN0526/tmd-top: Real-time monitoring of Linux process n...
👍4