public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply feedback

Browse Source
This commit is contained in:
Tom Lebreux
2025-03-19 15:09:50 -04:00
parent 1391623ae5
commit 1bf1ac8ba3
2 changed files with 6 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/extension-apiserver.md
+5 -15
View File
@@ -1,25 +1,15 @@
---
title: Extension Apiserver
title: Extension API Server
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/api/extension-apiserver"/>
</head>
Rancher extends Kubernetes with additional APIs by registering an extension
apiserver using [Kubernetes's Aggregation
layer](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/).
Rancher extends Kubernetes with additional APIs by registering an extension API server using the [Kubernetes API Aggregation Layer](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/).
## Disabling the extension apiserver
## Disabling the extension API server
The [aggregation layer must be
configured](https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/)
on the local Kubernetes cluster for the `imperative-api-extension` feature to be
enabled and to work correctly. The feature assumes this is configured and is
enabled by default. If it is not possible to configure the aggregation layer for
your local Kubernetes cluster, then you must turn off the feature.
The [aggregation layer must be configured](https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/) on the local Kubernetes cluster for the `imperative-api-extension` feature to be enabled and to work correctly. The feature assumes this is configured and is enabled by default. If it is not possible to configure the aggregation layer for your local Kubernetes cluster, then you must disable the feature. The `imperative-api-extension` feature flag can be disabled by either using the [Rancher UI](../how-to-guides/advanced-user-guides/enable-experimental-features#disabling-features-with-the-rancher-ui) or [Rancher API](../how-to-guides/advanced-user-guides/enable-experimental-features#disabling-features-with-the-rancher-api).
It will still be possible to access the additional APIs when the feature is
turned off. The additional APIs are available at `https://<rancher url>/ext` and
they are compatible with Kubernetes apiserver. This means you can use `curl` or
even `kubectl` to interact with the APIs.
It will still be possible to access the additional APIs when the feature is disabled. The additional APIs are available at `https://<rancher url>/ext` and they are compatible with the Kubernetes apiserver. This means you can use `curl` or `kubectl` to interact with the APIs.