Kubernetes

Building an In-House Dev Environment on Kubernetes Part 3: Kubernetes Device Plugin for LPU Hello! I’m Younghoon Jun, a DevOps Engineer on the ML team at HyperAccel. This post is the third installment of the Building an In-House Dev Environment on Kubernetes series! In Part 1, we covered the background, overall design, and direction of building a Kubernetes-based development environment. Part 2 introduced the strategy and process for building an ARC-based CI/CD infrastructure to overcome the structural limitations of self-hosted runners. In this third article, we will discuss the Device Plugin required for utilizing custom resources on Kubernetes. ...

The complete journey of redesigning HyperAccel’s CI/CD infrastructure based on Actions Runner Controller (ARC), including Vault JWT/Kubernetes Auth dual integration, and achieving pipeline observability through a custom-built Go-based Prometheus Exporter.

Building an Internal Development Environment with Kubernetes Chapter 1: Why Kubernetes? Hello! I’m Younghoon Jun, a DevOps Engineer on the ML team at HyperAccel. For those of you reading this, what kind of environment do you develop in? I imagine you’re working in various environments—local setups, SSH server access, cloud services, and more. HyperAccel develops on an environment built on top of a Kubernetes cluster. We spin up Pods based on devcontainers pre-configured with the packages needed for development, then connect to the container to do our work. To make things easier for our internal developers, we’ve created and provided a Devcontainer Portal. ...