When #861 merges, the EnvoyProxy custom resource can be used to customize the managed proxy infrastructure through gatewayclass.spec.parametersRef. Deleting the EnvoyProxy referenced by a managed GatewayClass can result in significant unintended consequences. Should EG finalize an EnvoyProxy referenced by a managed GatewayClass to avoid this potential issue?
When #861 merges, the EnvoyProxy custom resource can be used to customize the managed proxy infrastructure through
gatewayclass.spec.parametersRef. Deleting the EnvoyProxy referenced by a managed GatewayClass can result in significant unintended consequences. Should EG finalize an EnvoyProxy referenced by a managed GatewayClass to avoid this potential issue?