Version: v1.2

UI-Schema

KubeVela designs and implements the UI-Schema specification for the scalability of components, workflow steps, and operation and maintenance feature resources, in the case of variable input parameters, to achieve a more native UI experience.

At present, the UI-Schema specification mainly acts on the data input side and will be extended to the data visualization side in the future.

How UI-Schema works

The components, workflow steps, and operation and maintenance feature types with different UI-Schema working principles are defined through CUE, which we call XDefinition, and almost every definition includes the definition of input parameters. for example:

  1. scaler: {
  2. type: "trait"
  3. annotations: {}
  4. labels: {}
  5. description: "Manually scale K8s pod for your workload which follows the pod spec in path 'spec.template'."
  6. attributes: {
  7. podDisruptive: false
  8. appliesToWorkloads: ["*"]
  9. }
  10. }
  11. template: {
  12. parameter: {
  13. // +usage=Specify the number of workload
  14. replicas: *1 | int
  15. }
  16. // +patchStrategy=retainKeys
  17. patch: spec: replicas: parameter.replicas
  18. }

In the above example, the user input parameter is replicas.

In the UI we want the user to be able to set the number of replicas via a number input form.

ui schema

Its workflow is in the figure above. The API Schema is generated through the defined CUE, and then the default UI Schema is generated through the API Schema. If there is a custom UI Schema, the default configuration is patched with the custom configuration. The UI renders the front-end page based on the final UI Schema.

The spec are as follows:

  1. - jsonKey: string field name
  2. label: string show name in UI
  3. description: string help info
  4. uiType: string the react component type in UI
  5. sort: int sort number
  6. validate: data validate rule.
  7. required: bool
  8. max: int
  9. min: int
  10. regular: string
  11. options: Optional, for select forms
  12. - label: string
  13. value: string
  14. subParameters:
  15. ...

Supported react component types

Basic form

  • Input
  • Number
  • Select
  • Switch
  • Radio
  • DatePicker
  • Textarea
  • Password

Business form

  • Ignore: There are subordinate fields, and the current field is not displayed.
  • ClusterSelect
  • EnvSelect
  • SecretSelect
  • SecretKeySelect
  • ComponentSelect
  • ImageInput
  • ClassStorageSelect
  • PVCSelect
  • CPUNumber
  • MemoryNumber
  • K8sObjectsCode

Combination form

  • KV
  • Strings
  • Structs
  • Group: render as a titled container
  • InnerGroup
  • TabGroup

How to expand

UI-Schema mainly extends front-end react components, refer to https://github.com/oam-dev/velaux/tree/main/src/extends