Rename Service APIs to Gateway API (#9347)

* Rename Service APIs to Gateway API

* update alias

Co-authored-by: craigbox <craigbox@google.com>

* fix missing url

Co-authored-by: craigbox <craigbox@google.com>
This commit is contained in:
Shamsher Ansari 2021-03-22 19:59:35 +05:30 committed by GitHub
parent f7a11de48a
commit f23fcb5fb0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 15 additions and 13 deletions

View File

@ -44,7 +44,7 @@ Below is our list of existing features and their current phases. This informatio
| CNI container interface | Alpha
| [Sidecar API](/docs/reference/config/networking/sidecar/) | Beta
| [DNS Proxying](/docs/ops/configuration/traffic-management/dns-proxy/) | Alpha
| [Kubernetes service-apis](/docs/tasks/traffic-management/ingress/service-apis/) | Alpha
| [Kubernetes service-apis](/docs/tasks/traffic-management/ingress/gateway-api/) | Alpha
### Observability

View File

@ -1,25 +1,27 @@
---
title: Kubernetes Service APIs
description: Describes how to configure the Kubernetes Service APIs with Istio.
title: Kubernetes Gateway API
description: Describes how to configure the Kubernetes Gateway API with Istio.
weight: 50
aliases:
- /docs/tasks/traffic-management/ingress/service-apis/
keywords: [traffic-management,ingress]
owner: istio/wg-networking-maintainers
test: yes
---
This task describes how to configure Istio to expose a service outside of the service mesh cluster, using the Kubernetes [Service APIs](https://kubernetes-sigs.github.io/gateway-api/).
This task describes how to configure Istio to expose a service outside of the service mesh cluster, using the Kubernetes [Gateway API](https://gateway-api.sigs.k8s.io/).
These APIs are an actively developed evolution of the Kubernetes [Service](https://kubernetes.io/docs/concepts/services-networking/service/)
and [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) APIs.
## Setup
1. Install the Service APIs CRDs:
1. Install the Gateway API CRDs:
{{< text bash >}}
$ kubectl kustomize "github.com/kubernetes-sigs/service-apis/config/crd?ref=v0.1.0" | kubectl apply -f -
$ kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.2.0" | kubectl apply -f -
{{< /text >}}
1. Install Istio, or reconfigure an existing installation to enable the Service APIs controller:
1. Install Istio, or reconfigure an existing installation to enable the Gateway API controller:
{{< text bash >}}
$ istioctl install --set values.pilot.env.PILOT_ENABLED_SERVICE_APIS=true
@ -29,7 +31,7 @@ and [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)
## Configuring a Gateway
See the [Service APIs](https://kubernetes-sigs.github.io/gateway-api/) documentation for information about the APIs.
See the [Gateway API](https://gateway-api.sigs.k8s.io/) documentation for information about the APIs.
1. Deploy a test application:
@ -37,7 +39,7 @@ See the [Service APIs](https://kubernetes-sigs.github.io/gateway-api/) documenta
$ kubectl apply -f @samples/httpbin/httpbin.yaml@
{{< /text >}}
1. Deploy the Service APIs configuration:
1. Deploy the Gateway API configuration:
{{< text bash >}}
$ kubectl apply -f - <<EOF

View File

@ -17,11 +17,11 @@
####################################################################################################
# WARNING: THIS IS AN AUTO-GENERATED FILE, DO NOT EDIT. PLEASE MODIFY THE ORIGINAL MARKDOWN FILE:
# docs/tasks/traffic-management/ingress/service-apis/index.md
# docs/tasks/traffic-management/ingress/gateway-api/index.md
####################################################################################################
snip_setup_1() {
kubectl kustomize "github.com/kubernetes-sigs/service-apis/config/crd?ref=v0.1.0" | kubectl apply -f -
kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.2.0" | kubectl apply -f -
}
snip_setup_2() {

View File

@ -58,9 +58,9 @@ Istio continues to make mesh telemetry collection more configurable. In this rel
[Request Classification](/docs/tasks/observability/metrics/classify-metrics/) has been promoted to Beta. This feature
enables users to more precisely understand and monitor the traffic in their service mesh.
## Kubernetes Service API support (Alpha)
## Kubernetes Gateway API support (Alpha)
Configuring Istio to expose a service using [Kubernetes Service APIs](https://kubernetes-sigs.github.io/service-apis/) has been an active area of development since Istio 1.6, and we are pleased to announce support for them as Alpha in 1.9. Using these APIs benefits users who move between other service meshes that support these APIs. To try them out, check out the [Service API's getting started documentation](/docs/tasks/traffic-management/ingress/service-apis/).
Configuring Istio to expose a service using [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) has been an active area of development since Istio 1.6, and we are pleased to announce support for them as Alpha in 1.9. Using these APIs benefits users who move between other service meshes that support these APIs. To try them out, check out the [Gateway API getting started documentation](/docs/tasks/traffic-management/ingress/gateway-api/).
We are eager to evolve these CRDs in partnership with the Kubernetes community, notably the
[Kubernetes SIG-NETWORK group](https://github.com/kubernetes/community/tree/master/sig-network), in upcoming releases to