📚 This post is part of the Contribution envoy series (Part 8) View full series → 주제 및 배경 지난 회차에서는 bitfield_ro를 simpleCommands()에 추가해야 한다는 결론을 내렸다. 이번 회차에서는 변경 사항이 반영된 Envoy 바이너리를 week_5에서 구축한 Minikube 클러스터에 재배포하고, 새 명령어가 전체 경로에서 정상적으로 동작하는지 확인해보자. ...
📚 This post is part of the Contribution envoy series (Part 8) View full series → Background In the previous post (#6: Issue Analysis — Where do we add bitfield_ro?), we analyzed where the change should land and concluded that bitfield_ro belongs in simpleCommands(). In this post, we will redeploy the Envoy binary with that change into the Minikube cluster we set up in week_5 and confirm that the new command works end-to-end. ...
📚 This post is part of the Contribution envoy series (Part 7) View full series → 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. ...
📚 This post is part of the Contribution envoy series (Part 7) View full series → 주제 및 배경 지난 회차(#5: Custom Envoy Proxy Deployment)에서는 직접 빌드한 Envoy를 Minikube 클러스터에 배포하고, Redis에 직접 붙었을 때와 Envoy를 경유했을 때의 응답 차이를 비교해 bitfield_ro 명령어가 프록시에서 unknown command로 떨어지는 것을 확인했다. ...
📚 This post is part of the Contribution envoy series (Part 6) View full series → 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. ...
📚 This post is part of the Contribution envoy series (Part 6) View full series → 주제 및 배경 지난 회차(#4: Envoy Proxy Build)에서는 Bazel로 Envoy Proxy를 빌드한 뒤, Minikube 위에 Envoy 공식 이미지(envoyproxy/envoy:v1.38-latest)와 Redis를 함께 띄워보았다. 그 회차의 목적은 쿠버네티스 인프라를 마련하는 것이었기 때문에, 실제로는 내가 만든 Envoy가 동작하는지까지는 검증하지 않았다. ...
📚 This post is part of the Contribution envoy series (Part 5) View full series → 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. ...
📚 This post is part of the Contribution envoy series (Part 5) View full series → 주제 및 배경 지난 시간에는 빌드를 위한 도커 이미지를 다운로드받고, 컨테이너를 켜는 것까지 진행했다. 이번 시간에는 그 컨테이너 안에서 Envoy Proxy를 빌드하고, Minikube 위에 Redis와 Envoy Proxy를 띄워 실제로 동작하는 모습을 확인해보자. ...
📚 This post is part of the Contribution envoy series (Part 4) View full series → 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. ...
📚 This post is part of the Contribution envoy series (Part 4) View full series → 주제 및 배경 지난 포스팅에서는 우리가 최종적으로 실행할 환경인 쿠버네티스(Minikube)를 구축했다. 이번 포스팅에서는 Envoy Proxy를 빌드할 수 있는 환경을 구축해보자. ...