Update status of aggregator in API overview doc (#9866)
* Update status of aggregator in API overview doc * fix link syntaxpull/9922/head
parent
3e422bfa9e
commit
910215288e
|
@ -109,8 +109,8 @@ There are two supported paths to extending the API with [custom resources](/docs
|
|||
|
||||
1. [CustomResourceDefinition](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/)
|
||||
is for users with very basic CRUD needs.
|
||||
1. Coming soon: users needing the full set of Kubernetes API semantics can implement their own apiserver
|
||||
and use the [aggregator](https://git.k8s.io/community/contributors/design-proposals/api-machinery/aggregated-api-servers.md)
|
||||
1. Users needing the full set of Kubernetes API semantics can implement their own apiserver
|
||||
and use the [aggregator](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/)
|
||||
to make it seamless for clients.
|
||||
|
||||
|
||||
|
@ -131,4 +131,4 @@ Other extensions resources can be enabled by setting `--runtime-config` on
|
|||
apiserver. `--runtime-config` accepts comma separated values. For example: to disable deployments and ingress, set
|
||||
`--runtime-config=extensions/v1beta1/deployments=false,extensions/v1beta1/ingress=false`
|
||||
|
||||
{{% /capture %}}
|
||||
{{% /capture %}}
|
||||
|
|
Loading…
Reference in New Issue