Hacker News Reader

ottodacaton We're shipping to ARM64 and x64 without duplicating pipelines

We’ve rolled out multi-arch support and wrote up how we’re deploying to both ARM64 and x86_64 — without maintaining two pipelines or duplicating YAML. Using Docker Build Cloud + CAEPE, we build once, test both, and deploy based on arch health. Covers routing workloads, running per-arch smoke tests, and handling selective rollbacks. Would love to hear how others are approaching this in prod.

ottodacaton Are you deploying across ARM and x64 architectures?

Hi HN,

We’re seeing more teams explore multi-architecture strategies — especially combining ARM (like AWS Graviton) and x64 workloads — to optimize for cost, performance, and infrastructure flexibility.

But deployment at scale is messy. CI/CD workflows get more complex, tooling becomes inconsistent, and governance often lags behind.

Curious how others are handling this:

• Are you running multi-arch builds in CI/CD? • How do you manage compatibility, testing, or manifest handling? • Are security, compliance, or org structure slowing you down?

We recently published a piece on the business case and real-world use cases here: https://caepe.sh/multi-architecture-arm-x64-at-scale/

Would love to hear how others are navigating this — especially at scale.

Thanks!

ottodacaton GitHub Actions and Caepe: Turbocharging Your CI/CD Pipeline (Part 1)

Exploring how one can use GitHub Actions to streamline enterprise Kubernetes application deployments with CAEPE, providing a powerful combination of automation and advanced deployment strategies.

ottodacaton How to Maximize Your Kubernetes Deployment Success with Smoke Testing

Why you need smoke testing for Kubernetes deployments, the typical requirements to set up smoke tests and how teams can streamline the smoke testing process with CAEPE.

ottodacaton An Enterprise DevOps Primer

Yes, DevOps is first culture & values. Without a mindset/value shift, the best tools won't help. Teams need to spend more time on articulating and communicating the purpose before getting caught in the implementation bits.

ottodacaton An Enterprise DevOps Primer

Hey, thanks for reading the article and sharing your thoughts. Totally get where you're coming from.

You're absolutely right that IT can be pretty complex, and just jumping on the latest trends without understanding the real deal isn't the way to go. This was meant to be a primer - a quick intro for those less familiar with the topic.

Indeed, understanding IT at a fairly low level is rare today as is NOT jumping on the next big thing without a clear idea of why you are doing something. This article was really meant to be an introduction to the top and there are so much more things to unpick.