-
-
Notifications
You must be signed in to change notification settings - Fork 47
Add new API object BackendRuntime for expandability #134
Copy link
Copy link
Closed
Labels
featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.needs-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.
Milestone
Description
Metadata
Metadata
Assignees
Labels
featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.needs-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What would you like to be added:
Right now, once we add a new backend support, we'll have to implement the
Backendinterface, and provide the default values, which means each time we want to support a new backend, we'll have to modify the controller logic. This is not that expandability considering Kubernetes has CRD intended for that. What's more, the default values can not be modified.So let's make them a CRD
Backendand export these default values by default, once admin wants to change the values, they can modify them directly.This required the support of helm installation.
Why is this needed:
Better expandability.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.