Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update docs from repo source #1499

Merged
merged 1 commit into from
Oct 31, 2023
+111 −4
Merged

chore(deps): update docs from repo source #1499

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
104 changes: 104 additions & 0 deletions app/docs/dev/crds/kuma.io_meshloadbalancingstrategies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -374,11 +374,115 @@ spec:
description: LocalityAwareness contains configuration for
locality aware load balancing.
properties:
crossZone:
description: CrossZone defines locality aware load balancing
priorities when dataplane proxies inside local zone
are unavailable
properties:
failover:
description: Failover defines list of load balancing
rules in order of priority
items:
properties:
from:
description: From defines the list of zones
to which the rule applies
properties:
zones:
items:
type: string
type: array
required:
- zones
type: object
to:
description: To defines to which zones the
traffic should be load balanced
properties:
type:
description: Type defines how target zones
will be picked from available zones
enum:
- None
- Only
- Any
- AnyExcept
type: string
zones:
items:
type: string
type: array
required:
- type
- zones
type: object
required:
- to
type: object
type: array
failoverThreshold:
description: 'FailoverThreshold defines the percentage
of live destination dataplane proxies below which
load balancing to the next priority starts. Example:
If you configure failoverThreshold to 70, and
you have deployed 10 destination dataplane proxies.
Load balancing to next priority will start when
number of live destination dataplane proxies drops
below 7. Default 50'
properties:
percentage:
anyOf:
- type: integer
- type: string
x-kubernetes-int-or-string: true
required:
- percentage
type: object
type: object
disabled:
description: Disabled allows to disable locality-aware
load balancing. When disabled requests are distributed
across all endpoints regardless of locality.
type: boolean
localZone:
description: LocalZone defines locality aware load balancing
priorities between dataplane proxies inside a zone
properties:
affinityTags:
description: AffinityTags list of tags for local
zone load balancing.
items:
properties:
key:
description: Key defines tag for which affinity
is configured
type: string
weight:
description: 'Weight of the tag used for load
balancing. The bigger the weight the bigger
the priority. Percentage of local traffic
load balanced to tag is computed by dividing
weight by sum of weights from all tags.
For example with two affinity tags first
with weight 80 and second with weight 20,
then 80% of traffic will be redirected to
the first tag, and 20% of traffic will be
redirected to second one. Setting weights
is not mandatory. When weights are not set
control plane will compute default weight
based on list order. Default: If you do
not specify weight we will adjust them so
that 90% traffic goes to first tag, 9% to
next, and 1% to third and so on.'
format: int32
type: integer
required:
- key
type: object
type: array
required:
- affinityTags
type: object
type: object
type: object
targetRef:
Expand Down
3 changes: 3 additions & 0 deletions app/docs/dev/kuma-cp.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -740,6 +740,9 @@ experimental:
fullResyncInterval: 60s # ENV: KUMA_EXPERIMENTAL_KDS_EVENT_BASED_WATCHDOG_FULL_RESYNC_INTERVAL
# If true, then initial full resync is going to be delayed by 0 to FullResyncInterval.
delayFullResync: false # ENV: KUMA_EXPERIMENTAL_KDS_EVENT_BASED_WATCHDOG_DELAY_FULL_RESYNC
# If true then control plane computes reachable services automatically based on MeshTrafficPermission.
# Lack of MeshTrafficPermission is treated as Deny the traffic.
autoReachableServices: false # ENV: KUMA_EXPERIMENTAL_AUTO_REACHABLE_SERVICES

proxy:
gateway:
Expand Down
8 changes: 4 additions & 4 deletions app/docs/raw/UPGRADE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,10 @@ New rule is applied for CREATE operations. The old rule is still applied for UPD

These endpoints are getting replaced to achieve more coherency on the API:

- `/meshes/{mesh}/zoneegressoverviews` moves to `/meshes/{mesh}/zoneegresses/-overview`
- `/meshes/{mesh}/zoneingresses+insights` moves to `/meshes/{mesh}/zone-ingresses/-overview`
- `/meshes/{mesh}/dataplanes+insights` moves to `/meshes/{mesh}/dataplanes/-overview`
- `/zones+insights` moves to `/zones/-overview`
- `/meshes/{mesh}/zoneegressoverviews` moves to `/meshes/{mesh}/zoneegresses/_overview`
- `/meshes/{mesh}/zoneingresses+insights` moves to `/meshes/{mesh}/zone-ingresses/_overview`
- `/meshes/{mesh}/dataplanes+insights` moves to `/meshes/{mesh}/dataplanes/_overview`
- `/zones+insights` moves to `/zones/_overview`

While you can use the old API they will be removed in a future version

Expand Down
Loading