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

Jump to bottom

chore(docs): correct typo in service discovery #1385

Merged
merged 1 commit into from
Jun 28, 2023
Merged

chore(docs): correct typo in service discovery #1385

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
2 changes: 1 addition & 1 deletion app/_src/networking/service-discovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
Connectivity among the `kuma-dp` instances can happen in two ways:

* In {% if_version lte:2.1.x %}[standalone mode](/docs/{{ page.version }}/deployments/stand-alone){% endif_version %}{% if_version gte:2.2.x %}[standalone mode](/docs/{{ page.version }}/production/deployment/stand-alone/){% endif_version %} `kuma-dp` processes communicate with each other in a flat networking topology. This means that every data-plane must be able to consume another data-plane by directly sending requests to its IP address. In this mode, every `kuma-dp` must be able to send requests to every other `kuma-dp` on the specific ports that govern service traffic, as described in the `kuma-dp` {% if_version lte:2.1.x %}[ports section](/docs/{{ page.version }}/networking/networking#kuma-dp-ports){% endif_version %}{% if_version gte:2.2.x %}[ports section](/docs/{{ page.version }}/production/dp-config/dpp#data-plane-proxy-ports){% endif_version %}.
* In {% if_version lte:2.1.x %}[multi-zone mode](/docs/{{ page.version }}/deployments/multi-zone){% endif_version %}{% if_version gte:2.2.x %}[multi-zone mode](/docs/{{ page.version }}/production/deployment/multi-zone/){% endif_version %}connectivity is being automatically resolved by {{site.mesh_product_name}} to either a data plane running in the same zone, or through the address of a {% if_version lte:2.1.x %}[zone egress proxy](/docs/{{ page.version }}/explore/zoneegress){% endif_version %}{% if_version gte:2.2.x %}[zone egress proxy](/docs/{{ page.version }}/production/cp-deployment/zoneegress/){% endif_version %} (if present) and {% if_version lte:2.1.x %}[zone ingress proxy](/docs/{{ page.version }}/explore/zone-ingress){% endif_version %}{% if_version gte:2.2.x %}[zone ingress proxy](/docs/{{ page.version }}/production/cp-deployment/zone-ingress/){% endif_version %} in another zone for cross-zone connectivity. This means that multi-zone connectivity can be used to connect services running in different clusters, platforms or clouds in an automated way. {{site.mesh_product_name}} also creates a `.mesh` zone via its [native DNS resolver](/docs/{{ page.version }}/networking/dns/). The automatically created `kuma.io/zone` tag can be used with {{site.mesh_product_name}} policies in order to determine how traffic flow across a multi-zone setup.
* In {% if_version lte:2.1.x %}[multi-zone mode](/docs/{{ page.version }}/deployments/multi-zone){% endif_version %}{% if_version gte:2.2.x %}[multi-zone mode](/docs/{{ page.version }}/production/deployment/multi-zone/){% endif_version %}connectivity is being automatically resolved by {{site.mesh_product_name}} to either a data plane running in the same zone, or through the address of a {% if_version lte:2.1.x %}[zone egress proxy](/docs/{{ page.version }}/explore/zoneegress){% endif_version %}{% if_version gte:2.2.x %}[zone egress proxy](/docs/{{ page.version }}/production/cp-deployment/zoneegress/){% endif_version %} (if present) and {% if_version lte:2.1.x %}[zone ingress proxy](/docs/{{ page.version }}/explore/zone-ingress){% endif_version %}{% if_version gte:2.2.x %}[zone ingress proxy](/docs/{{ page.version }}/production/cp-deployment/zone-ingress/){% endif_version %} in another zone for cross-zone connectivity. This means that multi-zone connectivity can be used to connect services running in different clusters, platforms or clouds in an automated way. {{site.mesh_product_name}} also creates a `.mesh` zone via its [native DNS resolver](/docs/{{ page.version }}/networking/dns/). The automatically created `kuma.io/zone` tag can be used with {{site.mesh_product_name}} policies in order to determine how traffic flows across a multi-zone setup.

Check warning on line 29 in app/_src/networking/service-discovery.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('be used').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('be used').", "location": {"path": "app/_src/networking/service-discovery.md", "range": {"start": {"line": 29, "column": 977}}}, "severity": "INFO"}

Check failure on line 29 in app/_src/networking/service-discovery.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'DNS' instead of 'dns'.

Raw Output:
{"message": "[Vale.Terms] Use 'DNS' instead of 'dns'.", "location": {"path": "app/_src/networking/service-discovery.md", "range": {"start": {"line": 29, "column": 1198}}}, "severity": "ERROR"}

Check warning on line 29 in app/_src/networking/service-discovery.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('be used').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('be used').", "location": {"path": "app/_src/networking/service-discovery.md", "range": {"start": {"line": 29, "column": 1254}}}, "severity": "INFO"}

Check warning on line 29 in app/_src/networking/service-discovery.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.WordList] Use 'to' instead of 'in order to'.

Raw Output:
{"message": "[Google.WordList] Use 'to' instead of 'in order to'.", "location": {"path": "app/_src/networking/service-discovery.md", "range": {"start": {"line": 29, "column": 1303}}}, "severity": "WARNING"}

{% tip %}
By default cross-zone connectivity requires [mTLS](/docs/{{ page.version }}/policies/mutual-tls) to be enabled on the {% if_version lte:2.1.x %}[Mesh](/docs/{{ page.version }}/policies/mesh){% endif_version %}{% if_version gte:2.2.x %}[Mesh](/docs/{{ page.version }}/production/mesh/){% endif_version %} with the appropriate [Traffic Permission](/docs/{{ page.version }}/policies/traffic-permissions) to enable the flow of traffic. Otherwise, unsecured traffic won't be permitted outside each zone.
Expand Down
Loading