Bug 1478926 - [RFE] API based storage for UAS
Summary: [RFE] API based storage for UAS
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Eric Paris
QA Contact: Xiaoli Tian
URL: https://github.com/kubernetes/kuberne...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-07 13:56 UTC by Fabian Deutsch
Modified: 2019-01-16 08:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-16 08:38:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2017-08-07 13:56:10 UTC
Description of problem:
KubeVirt is relying on User API Servers and API Server aggregation.
For several reasons, discussed upstream in https://github.com/kubernetes/kubernetes/issues/46351, Kubernetes should provide a way to store custom API Server objections (following certain conventions) in the Kube API Server.
This would prevent that UAS implementaqtions need to introduce their own object store.

Version-Release number of selected component (if applicable):
Current

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Fabian Deutsch 2019-01-16 08:38:40 UTC
We are using CRDs with admission controllers, as well as subresources and stateless API servres for streaming endpoints.


Note You need to log in before you can comment on or make changes to this bug.