Skip to content

Add new API object BackendRuntime for expandability #134

@kerthcet

Description

@kerthcet

What would you like to be added:

Right now, once we add a new backend support, we'll have to implement the Backend interface, 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 Backend and 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:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureCategorizes issue or PR as related to a new feature.needs-priorityIndicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions