Extending Kubernetes: Difference between revisions
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* [[Kubernetes Development#Subjects|Kubernetes Development]] | * [[Kubernetes Development#Subjects|Kubernetes Development]] | ||
* [[Kubernetes Concepts#Subjects|Kubernetes Concepts]] | * [[Kubernetes Concepts#Subjects|Kubernetes Concepts]] | ||
=Kubernetes Aggregation Layer= | =Kubernetes Aggregation Layer= | ||
| Line 17: | Line 10: | ||
{{Internal|Kubernetes Custom Resources|Custom Resources}} | {{Internal|Kubernetes Custom Resources|Custom Resources}} | ||
=Differences between Custom Resources and Extension API Servers= | |||
=Differences between | |||
* An extension API server can use different storage APIs rather than etcdv3 | * An extension API server can use different storage APIs rather than etcdv3 | ||
* Extends long-running subresources/endpoints like websocket for your own resources | * Extends long-running subresources/endpoints like websocket for your own resources | ||
| Line 28: | Line 16: | ||
=Operator Pattern= | =Operator Pattern= | ||
{{Internal|Kubernetes Operators Concepts|Kubernetes Operators Concepts}} | |||
Latest revision as of 02:03, 14 October 2020
External
Internal
Kubernetes Aggregation Layer
Kubernetes Custom Resources
Differences between Custom Resources and Extension API Servers
- An extension API server can use different storage APIs rather than etcdv3
- Extends long-running subresources/endpoints like websocket for your own resources
- Integrates your apiserver with whatever external systems