[StackOverflow/kubernetes] Is Kgateway an Envoy fork?

### ROOT CAUSE The confusion likely stems from the fact that both Kuma and Envoy are service mesh components, but they serve different purposes. Kuma is a control plane, while Envoy is a data plane proxy. Kuma does not fork Envoy; instead, it uses Envoy as its underlying proxy. ### CODE FIX 1. **Clarify the Relationship**: Kuma Gateway leverages Envoy as its data plane but does not fork it. Kuma focuses on the control plane (e.g., configuration, traffic management), while Envoy handles the actual proxying of traffic. - **Action**: Ensure users understand that Kuma integrates with Envoy rather than being a derivative. 2. **Check Project Documentation**: Verify the specific project (e.g., Kuma) to confirm if it uses Envoy directly or through a wrapper. For instance, Kuma deploys Envoy as sidecar proxies but does not modify its core code. - **Action**: Consult the project’s GitHub or documentation for details on Envoy integration. 3. **Avoid Confusion with Similar Projects**: Some projects (e.g., Gloo or Aspen Mesh) might fork Envoy for customization. Kuma does not fall into this category. - **Action**: If the user is comparing projects, clarify their functional differences. **Example Command to Deploy Kuma with Envoy**: ```bash kumactl install kuma | kubectl apply -f - ``` This command deploys Kuma, which configures Envoy proxies but does not alter Envoy’s codebase. By addressing the misconception and emphasizing integration over derivation, users can avoid conflating the two projects.