open-source on Qerogram의 IT 삽질기 | Qerogram's IT Journal

[EN] Contributing to Envoy Proxy #6: Issue Analysis — Where do we add bitfield_ro?

Sun, 09 Aug 2026 12:00:00 +0900

Background

In the previous post (#5: Custom Envoy Proxy Deployment), I deployed a self-built Envoy into a Minikube cluster and compared the responses from accessing Redis directly versus going through the Envoy proxy. We confirmed that the bitfield_ro command is rejected as an unknown command by the proxy.

[KR] Envoy Proxy 기여 여정 #6: 이슈 분석 - bitfield_ro는 어디에 추가하는가

Sun, 09 Aug 2026 12:00:00 +0900

주제 및 배경

지난 회차(#5: Custom Envoy Proxy Deployment)에서는 직접 빌드한 Envoy를 Minikube 클러스터에 배포하고, Redis에 직접 붙었을 때와 Envoy를 경유했을 때의 응답 차이를 비교해 bitfield_ro 명령어가 프록시에서 unknown command로 떨어지는 것을 확인했다.

[EN] Contributing to Envoy Proxy #5: Custom Envoy Proxy Deployment

Sun, 26 Jul 2026 12:00:00 +0900

Overview

In the previous post (#4: Envoy Proxy Build), we built Envoy with Bazel and brought up Envoy and Redis on Minikube — but using the official Envoy image (envoyproxy/envoy:v1.38-latest). That post was focused on getting the Kubernetes infrastructure in place, so we never actually verified that our custom-built binary worked end-to-end.

[KR] Envoy Proxy 기여 여정 #5: Custom Envoy Proxy Deployment

Sun, 26 Jul 2026 12:00:00 +0900

주제 및 배경

지난 회차(#4: Envoy Proxy Build)에서는 Bazel로 Envoy Proxy를 빌드한 뒤, Minikube 위에 Envoy 공식 이미지(envoyproxy/envoy:v1.38-latest)와 Redis를 함께 띄워보았다. 그 회차의 목적은 쿠버네티스 인프라를 마련하는 것이었기 때문에, 실제로는 내가 만든 Envoy가 동작하는지까지는 검증하지 않았다.

Contributing to Envoy Proxy #4: Building Envoy Proxy

Sun, 12 Jul 2026 12:00:00 +0900

Overview

In the previous post, we pulled the build image and brought up its container. With the build environment ready, this time we will actually build Envoy Proxy inside that container, then bring up Redis and Envoy Proxy on Minikube to see the whole stack running end to end.

[EN] Contributing to Envoy Proxy #3: Setting Up the Build Environment — Part 2

Sun, 28 Jun 2026 12:00:00 +0900

Overview

In the previous post, we brought up the Kubernetes cluster — minikube — where our modified Envoy will eventually run. With the runtime environment in place, we now turn to the other half of the equation: a working build environment.

[EN] Contributing to Envoy Proxy #1: Setting Up the Development Environment

Sun, 31 May 2026 22:00:00 +0900

Introduction

As we begin this series, you’re likely already familiar with how remarkable Envoy Proxy is. It serves as a de facto standard proxy even in Istio environments and stands as one of the most mature and production-ready proxies available today. Envoy is the third CNCF project to achieve Graduated status.

[KR] Envoy Proxy 기여 여정 #1: 개발 환경 구축

Sun, 31 May 2026 22:00:00 +0900

들어가며

본 시리즈를 시작하며, Envoy Proxy가 얼마나 대단한 지는 다들 아실거라고 생각합니다. Istio환경에서도 실질적으로 표준에 준하는 Proxy이자, 굉장히 성숙도가 높은 Proxy입니다. CNCF의 3번째 Graduated Project입니다.

[EN] Contributing to Envoy Proxy: A Journey with Redis Integration

Tue, 19 May 2026 22:00:00 +0900

Overview and Background

This series documents how to implement and contribute Redis proxy features to Envoy Proxy, covering the entire journey from development environment setup to merging a contribution into the Envoy project. Rather than theoretical knowledge, this series shares practical experience from a real-world production scenario.