Support User Provisioned Envoy Proxy fleet

[arkodg]

Description:
It is hard to support all Kubernetes knobs for Deployment and Service within our EnvoyProxy API to customize EnvoyProxy Fleet resources, so its easier to allow users to create and update the envoy proxy fleet themselves, and use Envoy Gateway only to retrieve Xds Configuration

Here are the following things we need to do if this is something we want to support

• Disable the Infra Manager and support User Provisioned Envoy Proxy fleet
• Provide helm charts to create the Envoy Fleet resources (Service, Deployment)
• Add helm knobs to specify
  • Xds Server URL
  • TLS Credentials
  • Labels for Envoy Deployment and Service

[qicz]

IMO, supporting user-provisioned fleet, it is hard to config the XDS server and it would be inconvenient to extend more features. how we can support Wasm?

the infra manager can manage the envoy proxy easily.

support all Kubernetes knobs for Development and Service is hard but we can keep the frequently-used knobs only.

[arkodg]

this is not ideal from the project perspective since its another layer of customizations/support burden but it seems to be something many users want

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[arkodg]

with this approach, some features such as EnvoyProxy.Spec.Telemetry.Metrics would need to be caveated since those fields edit the bootstrap file in Envoy https://github.com/envoyproxy/gateway/blob/main/internal/xds/bootstrap/bootstrap.yaml.tpl which EG might not have access to for this BYO case