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

fix: remove some reference to generated and move use-kuma to use-mesh #1413

Merged
merged 4 commits into from
Jul 12, 2023
Merged

fix: remove some reference to generated and move use-kuma to use-mesh #1413

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1cc3a50
fix: remove some reference to generated and remove a line break
lahabana Jul 12, 2023
729ff7b
fix: rename use-kuma to use-mesh
lahabana Jul 12, 2023
5e17b80
correct path
lahabana Jul 12, 2023
e0d8566
clean redirects and stuff
lahabana Jul 12, 2023
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
4 changes: 2 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,10 @@ jobs:
max_timeout: 1200
- name: link checker
run: |
$(go env GOPATH)/bin/muffet ${URL} --buffer-size 8192 --exclude https://twitter.com --max-connections-per-host=8 --exclude 127.0.0.1 --exclude 'https://github.com/kumahq/kuma/pull' --exclude 'https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md.*' --rate-limit 50 --timeout 60
$(go env GOPATH)/bin/muffet ${URL} --buffer-size 8192 --exclude https://twitter.com --max-connections-per-host=8 --exclude 127.0.0.1 --exclude 'https://github.com/kumahq/kuma/pull' --exclude 'https://github.com//kumahq/kuma/pull' --exclude 'https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md.*' --rate-limit 50 --timeout 60
- name: link checker dev docs
run: |
$(go env GOPATH)/bin/muffet ${URL}/docs/dev --buffer-size 8192 --exclude https://twitter.com --max-connections-per-host=8 --exclude 127.0.0.1 --exclude 'https://github.com/kumahq/kuma/pull' --exclude 'https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md.*' --exclude https://download.konghq.com --rate-limit 50 --timeout 60
$(go env GOPATH)/bin/muffet ${URL}/docs/dev --buffer-size 8192 --exclude https://twitter.com --max-connections-per-host=8 --exclude 127.0.0.1 --exclude 'https://github.com/kumahq/kuma/pull' --exclude 'https://github.com//kumahq/kuma/pull' --exclude 'https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md.*' --exclude https://download.konghq.com --rate-limit 50 --timeout 60

installer-sh:
name: Test installer.sh
Expand Down
7 changes: 0 additions & 7 deletions app/_common_redirects
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,12 +35,5 @@
/docs/:version/documentation/deployments/ /docs/:version/introduction/deployments 301

# kuma IA redirects (pages that do exist take precedence on these so it's safe to use `:version` for pages moved in newer versions).
/docs/:version/deployments/multi-zone /docs/:version/production/cp-deployment/multi-zone/
/docs/:version/deployments/stand-alone /docs/:version/production/cp-deployment/stand-alone/
/docs/:version/introduction/what-is-a-service-mesh/ /docs/:version/introduction/about-service-meshes
/docs/:version/introduction/what-is-kuma/ /docs/:version/introduction/overview-of-kuma
/docs/:version/introduction/deployments /docs/:version/production/deployment/
/docs/:version/policies/mesh /docs/:version/production/mesh/
/docs/:version/policies/proxy-template/ /docs/:version/reference/proxy-template/
/docs/:version/explore/dpp/* /docs/:version/production/dp-config/dpp/
/docs/:version/installation/* /docs/:version/production/install-kumactl/
2 changes: 1 addition & 1 deletion app/_data/docs_nav_kuma_2.2.x.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ items:
- text: Install kumactl
url: /production/install-kumactl/
- text: Use Kuma
url: /production/use-kuma/
url: /production/use-mesh/
- title: Control plane deployment
group: true
items:
Expand Down
2 changes: 1 addition & 1 deletion app/_data/docs_nav_kuma_2.3.x.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ items:
- text: Install kumactl
url: /production/install-kumactl/
- text: Use Kuma
url: /production/use-kuma/
url: /production/use-mesh/
- title: Control plane deployment
group: true
items:
Expand Down
2 changes: 1 addition & 1 deletion app/_data/docs_nav_kuma_dev.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ items:
- text: Install kumactl
url: /production/install-kumactl/
- text: Use Kuma
url: /production/use-kuma/
url: /production/use-mesh/
- title: Control plane deployment
group: true
items:
Expand Down
8 changes: 4 additions & 4 deletions app/_posts/2020-09-10-multi-cluster-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
Kuma creates a service connectivity overlay across hybrid infrastructure to discover and connect services automatically, including hybrid Kubernetes + VM services.
</i></center>

This [multi-zone capability](/docs/latest/deployments/multi-zone/) has been added in addition to the [multi-mesh support](/docs/latest/policies/mesh/) that Kuma introduced since day one to create multiple isolated meshes on the same cluster (with dedicated mTLS CAs) in order to reduce team coordination, increase isolation and improve security rather than one large service mesh that everybody is sharing. Also, since multi-zone leverages the first-class K8s + VM support that shipped since the first version of Kuma, all teams and workloads in the organizations can benefit from service mesh and not just our greenfield initiatives.
This [multi-zone capability](/docs/latest/production/cp-deployment/multi-zone/) has been added in addition to the [multi-mesh support](/docs/latest/production/mesh/) that Kuma introduced since day one to create multiple isolated meshes on the same cluster (with dedicated mTLS CAs) in order to reduce team coordination, increase isolation and improve security rather than one large service mesh that everybody is sharing. Also, since multi-zone leverages the first-class K8s + VM support that shipped since the first version of Kuma, all teams and workloads in the organizations can benefit from service mesh and not just our greenfield initiatives.

Check warning on line 19 in app/_posts/2020-09-10-multi-cluster-cloud.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 ('been added').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('been added').", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 19, "column": 85}}}, "severity": "INFO"}

Check warning on line 19 in app/_posts/2020-09-10-multi-cluster-cloud.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.Parens] Use parentheses judiciously.

Raw Output:
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 19, "column": 257}}}, "severity": "INFO"}

Check failure on line 19 in app/_posts/2020-09-10-multi-cluster-cloud.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'CAs'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'CAs'?", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 19, "column": 278}}}, "severity": "ERROR"}

Check warning on line 19 in app/_posts/2020-09-10-multi-cluster-cloud.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/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 19, "column": 283}}}, "severity": "WARNING"}

Check warning on line 19 in app/_posts/2020-09-10-multi-cluster-cloud.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.We] Try to avoid using first-person plural like 'our'.

Raw Output:
{"message": "[Google.We] Try to avoid using first-person plural like 'our'.", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 19, "column": 623}}}, "severity": "WARNING"}

A Kuma service mesh distributed across every cloud, cluster and workload that the teams are using can therefore be managed from one individual cluster of Kuma itself. Meanwhile, multiple service meshes can be virtually provisioned on one Kuma control plane (horizontally scalable) to simplify mesh management across the organization – very similar to how Kubernetes and its namespaces work.

Expand Down Expand Up @@ -67,7 +67,7 @@

1. A new “ingress” data plane proxy mode processes incoming traffic into a zone. There will be one Kuma ingress deployment per zone, that can be scaled horizontally as the traffic increases. The “ingress” data plane mode is being added in addition to the default proxying one and the “gateway” one (to support third-party API gateways). Because of the new “ingress” mode, Kuma doesn’t require a flat networking topology between zones and can support more complex infrastructure.
2. A built-in service discovery DNS server resolves the address of a service to either an IP address of a replica in the same zone or the address of an ingress proxy in another zone.
Likewise with the “global” and “remote” control planes, the ingress and the DNS service discovery can also be installed in one click by following the [multi-zone instructions](/docs/latest/deployments/multi-zone/) on Kuma.
Likewise with the “global” and “remote” control planes, the ingress and the DNS service discovery can also be installed in one click by following the [multi-zone instructions](/docs/latest/production/cp-deployment/multi-zone/) on Kuma.

Check warning on line 70 in app/_posts/2020-09-10-multi-cluster-cloud.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 installed').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('be installed').", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 70, "column": 111}}}, "severity": "INFO"}

When it comes to service discovery, Kuma creates a “.mesh” DNS entry on the built-in DNS resolver that can be used to resolve services across the same zone or in other zones, effectively “flattening” the discovery of services across a complex infrastructure. Kuma will – accordingly to the traffic routing policies that have been configured – determine if we should be consuming a replica of the service in the local zone or if we should resolve the request to the IP address of a Kuma ingress in another zone, which will then leverage SNI to determine what service has been requested and route the request accordingly.

Expand All @@ -77,15 +77,15 @@

Since SNI resolution is mandatory for cross-zone communication, the [mTLS policy](/docs/latest/policies/mutual-tls/) must be enabled on the mesh. Also, since Kuma already knows where all the services are running, cross-zone discovery and connectivity happen automatically.

When a new service is registered into Kuma, a new “kuma.io/zone” tag is added to the data plane definition so that we can use the [attribute-based policy selectors](/docs/latest/explore/dpp/#tags) to configure Kuma policies like [Traffic Route](/docs/latest/policies/traffic-route/) to determine the behavior of cross-zone traffic (blue/green or canary across different zones, weighted traffic, as well as traffic shifting).
When a new service is registered into Kuma, a new “kuma.io/zone” tag is added to the data plane definition so that we can use the [attribute-based policy selectors](/docs/latest/production/dp-config/dpp/) to configure Kuma policies like [Traffic Route](/docs/latest/policies/traffic-route/) to determine the behavior of cross-zone traffic (blue/green or canary across different zones, weighted traffic, as well as traffic shifting).

Check warning on line 80 in app/_posts/2020-09-10-multi-cluster-cloud.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 ('is registered').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is registered').", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 80, "column": 20}}}, "severity": "INFO"}

Check warning on line 80 in app/_posts/2020-09-10-multi-cluster-cloud.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 ('is added').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is added').", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 80, "column": 70}}}, "severity": "INFO"}

Check warning on line 80 in app/_posts/2020-09-10-multi-cluster-cloud.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.We] Try to avoid using first-person plural like 'we'.

Raw Output:
{"message": "[Google.We] Try to avoid using first-person plural like 'we'.", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 80, "column": 116}}}, "severity": "WARNING"}

Check warning on line 80 in app/_posts/2020-09-10-multi-cluster-cloud.md

View workflow job for this annotation

GitHub Actions / Lint docs 

[vale] reported by reviewdog 🐶
[Google.Parens] Use parentheses judiciously.

Raw Output:
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "app/_posts/2020-09-10-multi-cluster-cloud.md", "range": {"start": {"line": 80, "column": 340}}}, "severity": "INFO"}

When consuming any “{service-name}.mesh” on default port 80 (even if the service is not listening on port 80), the DNS resolver – in addition to resolving the address of the service – will also automatically resolve the port of the destination service and inject it into the connection in order to keep the uptime of the overall connectivity even when a team decides to re-assign ports of a service that other teams may be using. This feature reduces the team coordination required to maintain a large number of services and connections in a Kuma mesh.

### Conclusion

Thanks to the new multi-zone capability that Kuma provides since v0.6+, we can now easily run a service mesh across multiple Kubernetes clusters, clouds and regions. Since Kuma natively supports both containerized and VM workloads, this functionality can also be used to create service connectivity across hybrid architectures.

By providing [one-click installation steps](/docs/latest/documentation/deployments/) to automate the installation of new zones as well as features like global/remote control planes, built-in service discovery and a native Kuma ingress, Kuma abstracts away service connectivity by creating a network overlay that effectively flattens out how services can discover and consume each other across complex network topologies. This makes it a great fit for any enterprise or distributed environment.
By providing [one-click installation steps](/docs/latest/production/use-mesh) to automate the installation of new zones as well as features like global/remote control planes, built-in service discovery and a native Kuma ingress, Kuma abstracts away service connectivity by creating a network overlay that effectively flattens out how services can discover and consume each other across complex network topologies. This makes it a great fit for any enterprise or distributed environment.

To get up and running with Kuma, you can check out the [installation page](/install) as well as the official [Slack channel](/community).

Expand Down
2 changes: 1 addition & 1 deletion app/_src/explore/gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ These instructions are mostly taken from the [Kong docs](https://docs.konghq.com
1. [Install {{site.mesh_product_name}}](/docs/{{ page.version }}/installation/kubernetes) on your cluster and have the `default` [namespace labelled with sidecar-injection](/docs/{{ page.version }}/explore/dpp-on-kubernetes).
{% endif_version %}
{% if_version gte:2.2.x %}
1. [Install {{site.mesh_product_name}}](/docs/{{ page.version }}/production/use-kuma/) on your cluster and have the `default`[namespace labelled with sidecar-injection](/docs/{{ page.version }}/production/dp-config/dpp-on-kubernetes/).
1. [Install {{site.mesh_product_name}}](/docs/{{ page.version }}/production/use-mesh/) on your cluster and have the `default`[namespace labelled with sidecar-injection](/docs/{{ page.version }}/production/dp-config/dpp-on-kubernetes/).
{% endif_version %}

2. Install [Kong using helm](https://docs.konghq.com/kubernetes-ingress-controller/2.1.x/deployment/k4k8s/#helm).
Expand Down
2 changes: 1 addition & 1 deletion app/_src/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ The core maintainer of Kuma is **Kong**, the maker of the popular open-source Ko

[Explore the API](/docs/{{ page.version }}/reference/http-api)
{% endif_version %}
{% if_version gte:2.1.x %}
{% if_version gte:2.2.x %}
[Read about service mesh](/docs/{{ page.version }}/introduction/about-service-meshes)

[Read about Kuma](/docs/{{ page.version }}/introduction/overview-of-kuma)
Expand Down
2 changes: 1 addition & 1 deletion app/_src/introduction/how-kuma-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ By reducing the code that our teams create and maintain, we can modernize our ap
Out of the box, {{site.mesh_product_name}} ships with a bundled [Envoy](https://www.envoyproxy.io/) data plane proxy ready to use for our services, so that you don't have to worry about putting all the pieces together.

{% tip %}
{{site.mesh_product_name}} ships with an executable `kuma-dp` that executes the bundled `envoy` executable to create the data plane proxy. For details, see the [Overview](/docs/{{ page.version }}/introduction/overview-of-kuma).
{{site.mesh_product_name}} ships with an executable `kuma-dp` that executes the bundled `envoy` executable to create the data plane proxy. For details, see the [Overview]({%if_version lte:2.1.x %}/docs/{{ page.version }}/introduction/what-is-kuma{%endif_version%}{%if_version gte:2.2.x %}/docs/{{ page.version }}/introduction/overview-of-kuma{%endif_version%}).
{% endtip %}

[Install {{site.mesh_product_name}}](/install/) and follow the instructions to get up and running in a few steps.
Expand Down
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 @@ -17,7 +17,7 @@
While doing so, the data-planes also advertise the IP address of each service. The IP address is retrieved:

* On Kubernetes by looking at the address of the `Pod`.
* On Universal by looking at the inbound listeners that have been configured in the [`inbound` property](/docs/{{ page.version }}/generated/resources/proxy_dataplane) of the data-plane specification.
* On Universal by looking at the inbound listeners that have been configured in the [`inbound` property]({%if_version lte:2.1.x %}/docs/{{ page.version }}/explore/dpp-on-universal/{%endif_version%}{%if_version gte:2.2.x %}/docs/{{ page.version }}/production/dp-config/dpp-on-universal#dataplane-configuration{%endif_version%}) of the data-plane specification.

Check warning on line 20 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 ('been configured').

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

The IP address that's being advertised by every data-plane to the control-plane is also being used to route service traffic from one `kuma-dp` to another `kuma-dp`. This means that {{site.mesh_product_name}} knows at any given time what are all the IP addresses associated to every replica of every service. Another use-case where the IP address of the data-planes is being used is for metrics scraping by Prometheus.

Expand Down
4 changes: 1 addition & 3 deletions app/_src/policies/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,7 @@ title: Policies
---
Here you can find the list of Policies that {{site.mesh_product_name}} supports.

Going forward from version 2.0, {{site.mesh_product_name}} is transitioning from [source/destination policies](/docs/{{
page.version }}/policies/general-notes-about-kuma-policies) to [`targetRef` policies](/docs/{{ page.version
}}/policies/targetref).
Going forward from version 2.0, {{site.mesh_product_name}} is transitioning from [source/destination policies](/docs/{{ page.version }}/policies/general-notes-about-kuma-policies) to [`targetRef` policies](/docs/{{ page.version }}/policies/targetref).

The following table shows the equivalence between source/destination and `targetRef` policies:

Expand Down
8 changes: 5 additions & 3 deletions app/_src/production/cp-deployment/multi-zone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ The global control plane on Kubernetes must reside on its own Kubernetes cluster
{{site.mesh_namespace}} {{site.mesh_cp_name}} ClusterIP 10.105.12.133 <none> 5681/TCP,443/TCP,5676/TCP,5677/TCP,5678/TCP,5679/TCP,5682/TCP,5653/UDP 90s
```

By default, it's exposed on [port 5685]({% if_version lte:2.1.x %}/docs/{{ page.version }}/networking/networking{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/use-kuma#control-plane-ports{% endif_version %}). In this example the value is `35.226.196.103:5685`. You pass this as the value of `<global-kds-address>` when you set up the zone control planes.
By default, it's exposed on [port 5685]({% if_version lte:2.1.x %}/docs/{{ page.version }}/networking/networking{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/use-mesh#control-plane-ports{% endif_version %}). In this example the value is `35.226.196.103:5685`. You pass this as the value of `<global-kds-address>` when you set up the zone control planes.

{% endtab %}

Expand Down Expand Up @@ -216,7 +216,7 @@ You need the following values to pass to each zone control plane setup:

where `zone` is the same value for all zone control planes in the same zone.

Add `--egress-enabled` to list of arguments if you want to deploy optional [Zone Egress](/docs/{{ page.version }}/production/cp-deployment/zoneegress/).
Add `--egress-enabled` to list of arguments if you want to deploy optional [Zone Egress]({% if_version lte:2.1.x %}/docs/{{ page.version }}/explore/zoneegress/{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/cp-deployment/zoneegress/{% endif_version %}).

{% if_version gte:2.3.x %}
`--set {{site.set_flag_values_prefix}}controlPlane.tls.kdsZoneClient.skipVerify=true` is required because the default global control plane's certificate is self-signed.
Expand Down Expand Up @@ -254,7 +254,7 @@ You need the following values to pass to each zone control plane setup:

where `controlPlane.zone` is the same value for all zone control planes in the same zone.

Add `--set {{site.set_flag_values_prefix}}egress.enabled=true` to list of arguments if you want to deploy optional [Zone Egress](/docs/{{ page.version }}/production/cp-deployment/zoneegress/).
Add `--set {{site.set_flag_values_prefix}}egress.enabled=true` to list of arguments if you want to deploy optional [Zone Egress]({% if_version lte:2.1.x %}/docs/{{ page.version }}/explore/zoneegress/{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/cp-deployment/zoneegress/{% endif_version %}).

{% if_version gte:2.3.x %}
`--set {{site.set_flag_values_prefix}}controlPlane.tls.kdsZoneClient.skipVerify=true` is required because the default global control plane's certificate is self-signed.
Expand Down Expand Up @@ -522,3 +522,5 @@ spec:
With this setting, the global control plane will stop exchanging configuration with this zone.
As a result, the zone's ingress from zone-1 will be deleted from other zone and traffic won't be routed to it anymore.
The zone will show as **Offline** in the GUI and CLI.

[zoneegress]: https://kuma.io/docs/latest/security/zoneproxy-auth/
4 changes: 2 additions & 2 deletions app/_src/production/dp-config/transparent-proxying.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,11 @@ All incoming and outgoing traffic is automatically intercepted by `kuma-dp` with

## Universal

On **Universal** `kuma-dp` leverages the [data plane proxy specification](/docs/{{ page.version }}/generated/resources/proxy_dataplane) associated to it for receiving incoming requests on a pre-defined port.
On **Universal** `kuma-dp` leverages the [data plane proxy specification]({%if_version lte:2.1.x %}/docs/{{ page.version }}/explore/dpp-on-universal/{%endif_version%}{%if_version gte:2.2.x %}/docs/{{ page.version }}/production/dp-config/dpp-on-universal#dataplane-configuration{%endif_version%}) associated to it for receiving incoming requests on a pre-defined port.

There are several advantages for using transparent proxying in universal mode:

* Simpler [Dataplane resource](/docs/{{ page.version }}/generated/resources/proxy_dataplane), as the `outbound` section becomes obsolete and can be skipped.
* Simpler Dataplane resource, as the `outbound` section becomes obsolete and can be skipped.
* Universal service naming with `.mesh` [DNS domain](/docs/{{ page.version }}/networking/dns) instead of explicit outbound like `https://localhost:10001`.
* Support for hostnames of your choice using [VirtualOutbounds](/docs/{{ page.version }}/policies/virtual-outbound) that lets you preserve existing service naming.
* Better service manageability (security, tracing).
Expand Down
2 changes: 1 addition & 1 deletion app/_src/production/secure-deployment/api-server-auth.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Authentication with the API server
content_type: how-to
---

{{site.mesh_product_name}} exposes API server on [ports]({% if_version lte:2.1.x %}/docs/{{ page.version }}/networking/networking{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/use-kuma#control-plane-ports{% endif_version %}) `5681` and `5682` (protected by TLS).
{{site.mesh_product_name}} exposes API server on [ports]({% if_version lte:2.1.x %}/docs/{{ page.version }}/networking/networking{% endif_version %}{% if_version gte:2.2.x %}/docs/{{ page.version }}/production/use-mesh#control-plane-ports{% endif_version %}) `5681` and `5682` (protected by TLS).

An authenticated user can be authorized to execute administrative actions such as
* Managing administrative resources like {{site.mesh_product_name}} Secrets on Universal
Expand Down
0 app/_src/production/use-kuma.md → app/_src/production/use-mesh.md
View file
Open in desktop
File renamed without changes.
Loading