docs: Add Envoy Gateway install section

[kahirokunn]

Changes

• 🎁 Add Envoy Gateway install instructions to README

/kind documentation

Fixes #

Release Note

Add Envoy Gateway installation docs

Docs

N/A

[knative-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kahirokunn
Once this PR has been reviewed and has the lgtm label, please assign dsimansk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.45%. Comparing base (b658b58) to head (62bf6e7).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #891   +/-   ##
=======================================
  Coverage   76.45%   76.45%           
=======================================
  Files          17       17           
  Lines        1253     1253           
=======================================
  Hits          958      958           
  Misses        261      261           
  Partials       34       34           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kahirokunn]

@dprotaso Hello! I'd be grateful if you could leave a review when you have a moment! 🙏

[dprotaso]

is there a way to do this without helm?

[kahirokunn]

#891 (comment)

[dprotaso]

this is interesting - did they change where services are created?

[kahirokunn]

Envoy Gateway now has a new feature where it creates Services and Deployments in the Gateway resource's Namespace and assigns OwnerReferences.
This is the same implementation as many other Gateway controllers.
To utilize this, the following values are required:

third_party/envoy-gateway/helm/values-eg.yaml

I believe that using the GatewayNamespace is the best configuration, so I used Helm this time. What are your thoughts on this, @dprotaso ?

[dprotaso]

Sorry was at kubecon back now.

I'm wondering if we can keep the old installation and just remove the explicit overrides we have in EnvoyProxy etc in the external.yaml and internal.yaml file

net-gateway-api/third_party/envoy-gateway/external.yaml

Line 11 in feef669

namespace: envoy-gateway-system

[dprotaso]

I recall before that the name of the svc and namespace wasn't predictable

[dprotaso]

Though if we do that change then it might break upgrades which makes everything more complex.

Actually checking now we don't release the envoy yamls as part of the release so maybe we're ok in terms of what backwards compatibility we support.

[kahirokunn]

Glad to hear you were at KubeCon. I heard there were many exciting announcements this year, so I’m honestly a bit jealous you could attend.

With the namespaces separated in this way, the names of the created Services (and related resources) become fully predictable. Since we are not currently publishing the Envoy YAMLs as part of the official release artifacts, my feeling is that it would be better for the community if we focus less on backward compatibility here and instead present a clear best-practice configuration from the start.

What do you think about taking this approach?

[dprotaso]

if we focus less on backward compatibility here and instead present a clear best-practice configuration from the start.

Yeah I'm good with that approach

[dprotaso]

Can we still drop helm and just apply the single yaml file :P

[kahirokunn]

@dprotaso
I've completed it. Cloud you review again? 🙏