Skip to content

Commit 6e06a71

Browse files
committed
Add documentation explaining the difference between CRDs and API aggregation layer
1 parent 21de519 commit 6e06a71

File tree

1 file changed

+7
-0
lines changed
  • content/en/docs/concepts/extend-kubernetes/api-extension

1 file changed

+7
-0
lines changed

content/en/docs/concepts/extend-kubernetes/api-extension/_index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,10 @@
22
title: Extending the Kubernetes API
33
weight: 30
44
---
5+
6+
Custom resources are extensions of the Kubernetes API. Kubernetes provides two ways to add custom resources to your cluster:
7+
8+
- The [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/)
9+
API resource allows you to define a CRD object creates a new custom resource with a name and schema that you specify.
10+
The Kubernetes API serves and handles the storage of your custom resource. CRDs allow users to create new types of resources without adding another API server.
11+
- The [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) sits behind the primary API server, which acts as a proxy. This arrangement is called API Aggregation(AA). To users, the Kubernetes API appears extended.

0 commit comments

Comments
 (0)