Aller au contenu principal

Installation

Both Vstore and its Operator are in the same chart and will use the same values.

TiDB​

Operator​

Cluster​

Vstore​

Basic​

The configuration keys you can change are the following :

  • loglevel : Vstore log level

For these specific ones, refer to the Vstore documentation for more information :

  • config : The content of the Vstore configuration file.
  • identities : The content of the static initial identities config file.
  • model : The content of the static initial models config file.
  • policies : The content of the static initial policies config file.

Advanced​

The configuration keys you can change are the following :

  • replicaCount : The number of Vstore pods you want running
  • podAnnotations : Additional annotations to set on the pods. (shared config between Vstore and its operator)
  • podLabels : Additional labels to set on the pods. (shared config between Vstore and its operator)
  • resources:
    • limits : Limits describes the maximum amount of compute resources allowed. The kind cpu & memory are supported.
    • requests : Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. The kind cpu & memory are supported.

Operator​

The configuration keys you can change are the following :

  • podAnnotations : Additional annotations to set on the pods. (shared config between Vstore and its operator)
  • podLabels : Additional labels to set on the pods. (shared config between Vstore and its operator)
  • operator:
    • enabled: Whether the Operator should be installed along Vstore.
    • replicaCount: The number of Operator pods you want running
    • resources:
      • limits : Limits describes the maximum amount of compute resources allowed. The kind cpu & memory are supported.
      • requests : Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. The kind cpu & memory are supported.