Implementation: External Processing support

[izturn]

Signed-off-by: Gang Liu gang.liu@daocloud.io

Implementation proposal to address #5123

[izturn]

Due to the current proposal status, relevant unit tests have not been added yet

[codecov]

Codecov Report

Attention: Patch coverage is 17.76316% with 250 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@5b0d091). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
internal/dag/httpproxy_processor.go	28.98%	87 Missing and 11 partials ⚠️
internal/envoy/v3/listener.go	6.89%	54 Missing ⚠️
internal/envoy/v3/route.go	0.00%	42 Missing and 1 partial ⚠️
cmd/contour/serve.go	4.76%	20 Missing ⚠️
cmd/contour/servecontext.go	9.09%	19 Missing and 1 partial ⚠️
internal/xdscache/v3/listener.go	38.88%	11 Missing ⚠️
internal/fixture/httpproxy.go	0.00%	4 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5867   +/-   ##
=======================================
  Coverage        ?   80.06%           
=======================================
  Files           ?      133           
  Lines           ?    20279           
  Branches        ?        0           
=======================================
  Hits            ?    16237           
  Misses          ?     3736           
  Partials        ?      306           

Files with missing lines	Coverage Δ
internal/dag/dag.go	98.78% <ø> (ø)
internal/sorter/sorter.go	100.00% <ø> (ø)
pkg/config/parameters.go	88.05% <ø> (ø)
internal/fixture/httpproxy.go	86.27% <0.00%> (ø)
internal/xdscache/v3/listener.go	89.47% <38.88%> (ø)
cmd/contour/serve.go	21.36% <4.76%> (ø)
cmd/contour/servecontext.go	81.01% <9.09%> (ø)
internal/envoy/v3/route.go	76.56% <0.00%> (ø)
internal/envoy/v3/listener.go	91.13% <6.89%> (ø)
internal/dag/httpproxy_processor.go	85.40% <28.98%> (ø)

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[wilsonwu]

Let's review this PR again, this feature already ran on our product for 2 months, it is stable, we'd like to comtribute to community.

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[lorem-dev]

Anyone, please review it 🙏 🙏 🙏

[Hozeri]

Please review it

[lorem-dev]

@izturn, could you please squash the commits with linting fixes and format the commit messages as well?

[izturn]

@izturn, could you please squash the commits with linting fixes and format the commit messages as well?

ok, i will update it later

[izturn]

@izturn, could you please squash the commits with linting fixes and format the commit messages as well?

done

[donatgorbachev]

@skriss, could you please review this PR 🙏