Adds API to Manage Envoy Deployment

[danehans]

• Moves ProviderType to api/config/v1alpha1/shared_types.go since the types are being used by EnvoyGateway and EnvoyProxy APIs.
• Adds ResourceProvider type to EnvoyProxy API to define the desired state of supported infrastructure resources.
• Generates DeepCopy methods and CRD manifest.

xref #713

Signed-off-by: danehans daneyonhansen@gmail.com

[codecov-commenter]

Codecov Report

Merging #766 (7914962) into main (7e176de) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #766      +/-   ##
==========================================
+ Coverage   62.01%   62.03%   +0.01%     
==========================================
  Files          46       46              
  Lines        5995     5995              
==========================================
+ Hits         3718     3719       +1     
+ Misses       2043     2042       -1     
  Partials      234      234              

Impacted Files	Coverage Δ
internal/provider/kubernetes/helpers.go	73.38% <0.00%> (-0.81%)	⬇️
internal/provider/kubernetes/controller.go	52.22% <0.00%> (+0.38%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[arkodg]

@danehans this PR looks good, but prefer if we design and the deliver platform customizations in a future release (v0.4.0) so we scope out the exact type of platform customizations the project will support. For e.g. will the project also support HPA based replica fields ?

[danehans]

@arkodg thanks for the review and feedback. Since we have multiple requests for providing basic Envoy infra configurability, I disagree that we should wait to provide this feature:

xrefs:
#713
#648
#703

For e.g. will the project also support HPA based replica fields ?

I see HPA as "advanced configuration" that can be supported in the future.

@Xunzhuo @youngnick @skriss @AliceProxy WDYT?

[Alice-Lilith]

I definitely think that the Envoy infra should be customizable for the end user.

[arkodg]

I definitely think that the Envoy infra should be customizable for the end user.

agree @AliceProxy , im suggesting delaying this until its part of a roadmap theme

[danehans]

im suggesting delaying this until its part of a roadmap theme

IMHO we would prioritize features that are being requested by users. As I mention in #766 (comment), we have multiple requests to provide basic Envoy infra configurability.

[danehans]

Per our discussion during the 12/6/22 community meeting, @youngnick @AliceProxy @arkodg agreed to proceed with the general approach of this PR. The approach of this PR is consistent with the EnvoyGateway API and solves Envoy infra configurability that's being requested by the community. Since the API is alpha, we can take a broader approach to infra configurability, e.g. exposing spec, if we find this approach unmaintainable. @arkodg @AliceProxy @youngnick PTAL at this PR when you have a moment.

[Xunzhuo]

/lgtm
/approve

[Xunzhuo]

/hold

Can we rebase with main before getting this merged?

[danehans]

@Xunzhuo @arkodg @AliceProxy per #766 (comment) I rebased. Please retag when you have a moment.