Add support for ClientSideWeightedRoundRobin LB policy
Fixes https://github.com/projectcontour/contour/issues/6998
Hi @anton-kuklin! Welcome to our community and thank you for opening your first Pull Request. Someone will review it soon. Thank you for committing to making Contour better. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace
CC: @davinci26 @clayton-gonsalves @seth-epps @shadialtarsha @gregbarasch
Codecov Report
:x: Patch coverage is 94.02985% with 8 lines in your changes missing coverage. Please review.
:white_check_mark: Project coverage is 80.81%. Comparing base (cdf2738) to head (049fa51).
:warning: Report is 166 commits behind head on main.
| Files with missing lines | Patch % | Lines |
|---|---|---|
| internal/dag/extension_processor.go | 42.85% | 3 Missing and 1 partial :warning: |
| internal/dag/httpproxy_processor.go | 42.85% | 3 Missing and 1 partial :warning: |
Additional details and impacted files
@@ Coverage Diff @@
## main #6999 +/- ##
==========================================
+ Coverage 80.72% 80.81% +0.08%
==========================================
Files 131 131
Lines 19868 19996 +128
==========================================
+ Hits 16039 16159 +120
- Misses 3537 3543 +6
- Partials 292 294 +2
| Files with missing lines | Coverage Δ | |
|---|---|---|
| internal/dag/dag.go | 98.78% <ø> (ø) |
|
| internal/dag/policy.go | 96.02% <100.00%> (+0.34%) |
:arrow_up: |
| internal/envoy/v3/cluster.go | 96.97% <100.00%> (+0.66%) |
:arrow_up: |
| internal/dag/extension_processor.go | 93.87% <42.85%> (-2.56%) |
:arrow_down: |
| internal/dag/httpproxy_processor.go | 90.76% <42.85%> (-0.24%) |
:arrow_down: |
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
The Contour project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 30d of inactivity, lifecycle/stale is applied
- After 60d 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
The Contour project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 30d of inactivity, lifecycle/stale is applied
- After 60d 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
The Contour project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 30d of inactivity, lifecycle/stale is applied
- After 60d 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
The Contour project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 30d of inactivity, lifecycle/stale is applied
- After 60d 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
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