github.com/1aal/kubeblocks@v0.0.0-20231107070852-e1c03e598921/deploy/clickhouse-cluster/values.yaml (about)

     1  
     2  ## @param terminationPolicy define Cluster termination policy. One of DoNotTerminate, Halt, Delete, WipeOut.
     3  ##
     4  terminationPolicy: Halt
     5  
     6  ## Monitoring configurations
     7  monitor:
     8    ## @param monitor.enabled if `true`, enable Cluster monitor capabilities
     9    ##
    10    enabled: false
    11  
    12  ## Service configurations
    13  ##
    14  service:
    15    ## @param service.type ClickHouse service type, valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer.
    16    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
    17    ## 
    18    type: ClusterIP
    19  
    20  
    21  ## ClickHouse per shard component configurations
    22  ##
    23  clickhouse: 
    24    -
    25      ## @param clickhouse[*].replicaCount Number of ClickHouse replicas per shard to deploy
    26      ##
    27      replicaCount: 2
    28      ## ClickHouse workload pod resource requests and limits
    29      ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
    30      ## @param clickhouse[*].resources.limits The resources limits for the pod
    31      ## @param clickhouse[*].resources.requests The requested resources for the pod
    32      ##
    33      resources: {}
    34        # We usually recommend not to specify default resources and to leave this as a conscious
    35        # choice for the user. This also increases chances charts run on environments with little
    36        # resources, such as Minikube. If you do want to specify resources, uncomment the following
    37        # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    38        # limits:
    39        #   cpu: 100m
    40        #   memory: 128Mi
    41        # requests:
    42        #   cpu: 100m
    43        #   memory: 128Mi
    44      ## Enable persistence using Persistent Volume Claims
    45      ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
    46      ##
    47      persistence:
    48        ## @param clickhouse[*].persistence.enabled Enable persistence using Persistent Volume Claims
    49        ##
    50        enabled: false
    51        ## `data` volume settings
    52        ##
    53        data:
    54          ## @param clickhouse[*].persistence.data.storageClassName Storage class of backing PVC
    55          ## If defined, storageClassName: <storageClass>
    56          ## If set to "-", storageClassName: "", which disables dynamic provisioning
    57          ## If undefined (the default) or set to null, no storageClassName spec is
    58          ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    59          ##   GKE, AWS & OpenStack)
    60          ##
    61          storageClassName:
    62          ## @param clickhouse[*].persistence.size Size of data volume
    63          ##
    64          size: 10Gi
    65      ## @param clickhouse[*].tolerations Tolerations for ClickHouse pods assignment
    66      ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
    67      ##
    68      tolerations: []
    69  
    70    # -
    71    #   ## @param clickhouse[*].replicaCount Number of ClickHouse replicas per shard to deploy
    72    #   ##
    73    #   replicaCount: 2
    74    #   ## ClickHouse workload pod resource requests and limits
    75    #   ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
    76    #   ## @param clickhouse[*].resources.limits The resources limits for the init container
    77    #   ## @param clickhouse[*].resources.requests The requested resources for the init container
    78    #   ##
    79    #   resources: {}
    80    #     ## We usually recommend not to specify default resources and to leave this as a conscious
    81    #     ## choice for the user. This also increases chances charts run on environments with little
    82    #     ## resources, such as Minikube. If you do want to specify resources, uncomment the following
    83    #     ## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    84    #     ##
    85    #     # limits:
    86    #     #   cpu: 100m
    87    #     #   memory: 128Mi
    88    #     # requests:
    89    #     #   cpu: 100m
    90    #     #   memory: 128Mi
    91    #   ## Enable persistence using Persistent Volume Claims
    92    #   ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
    93    #   ##
    94    #   persistence:
    95    #     ## @param clickhouse[*].persistence.enabled Enable persistence using Persistent Volume Claims
    96    #     ##
    97    #     enabled: false
    98    #     ## `data` volume settings
    99    #     ##
   100    #     data:
   101    #       ## @param clickhouse[*].persistence.data.storageClassName Storage class of backing PVC
   102    #       ## If defined, storageClassName: <storageClass>
   103    #       ## If set to "-", storageClassName: "", which disables dynamic provisioning
   104    #       ## If undefined (the default) or set to null, no storageClassName spec is
   105    #       ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
   106    #       ##   GKE, AWS & OpenStack)
   107    #       ##
   108    #       storageClassName:
   109    #       ## @param clickhouse[*].persistence.size Size of data volume
   110    #       ##
   111    #       size: 10Gi
   112    #   ## @param clickhouse[*].tolerations Tolerations for ClickHouse pods assignment
   113    #   ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
   114    #   ##
   115    #   tolerations: []
   116  
   117  
   118  ## @param tolerations define global Tolerations for the cluster all pod's assignment
   119  ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
   120  ##
   121  tolerations: []
   122  
   123  
   124  ## @param topologySpreadConstraints Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template
   125  ## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#spread-constraints-for-pods
   126  ##
   127  topologyKeys:
   128    - kubernetes.io/hostname
   129  
   130  
   131  ## @param affinity is affinity setting for ClickHouse cluster pods assignment
   132  ##
   133  affinity: {}
   134  
   135  ## @param useClickHouseKeeper specify whether to use ClickHouse Keeper or Zookeeper
   136  ##
   137  useClickHouseKeeper: true
   138  
   139  ## Zookeeper/ClickHouse Keeper configuration
   140  ##
   141  keeper:
   142    ## @param keeper.replicaCount Number of Zookeeper/ClickHouse Keeper replicas
   143    ##
   144    replicaCount: 1
   145  
   146    ## Zookeeper/ClickHouse Keeper workload pod resource requests and limits
   147    ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
   148    ## @param clickhouse[*].resources.limits The resources limits for the init container
   149    ## @param clickhouse[*].resources.requests The requested resources for the init container
   150    ##
   151    resources: {}
   152      ## We usually recommend not to specify default resources and to leave this as a conscious
   153      ## choice for the user. This also increases chances charts run on environments with little
   154      ## resources, such as Minikube. If you do want to specify resources, uncomment the following
   155      ## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
   156      ##
   157      # limits:
   158      #   cpu: 100m
   159      #   memory: 128Mi
   160      # requests:
   161      #   cpu: 100m
   162      #   memory: 128Mi
   163  
   164    persistence:
   165      enabled: false
   166      data:
   167        storageClassName:
   168        size: 8Gi
   169  
   170    ## @param keeper.tolerations Tolerations for *Keeper pods assignment
   171    ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
   172    ##
   173    tolerations: []
   174  
   175  ## ClickHouse ingress parameters
   176  ## ref: http://kubernetes.io/docs/user-guide/ingress/
   177  ##
   178  ingress:
   179    ## @param ingress.enabled Enable ingress record generation for ClickHouse
   180    ##
   181    enabled: false
   182    ## @param ingress.pathType Ingress path type
   183    ##
   184    pathType: ImplementationSpecific
   185    ## @param ingress.apiVersion Force Ingress API version (automatically detected if not set)
   186    ##
   187    apiVersion: ""
   188    ## @param ingress.hostname Default host for the ingress record
   189    ##
   190    hostname: clickhouse.local
   191    ## @param ingress.ingressClassName IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)
   192    ## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster .
   193    ## ref: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/
   194    ##
   195    ingressClassName: ""
   196    ## @param ingress.path Default path for the ingress record
   197    ## NOTE: You may need to set this to '/*' in order to use this with ALB ingress controllers
   198    ##
   199    path: /
   200    ## @param ingress.annotations Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.
   201    ## Use this parameter to set the required annotations for cert-manager, see
   202    ## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations
   203    ## e.g:
   204    ## annotations:
   205    ##   kubernetes.io/ingress.class: nginx
   206    ##   cert-manager.io/cluster-issuer: cluster-issuer-name
   207    ##
   208    annotations: {}
   209    ## @param ingress.tls Enable TLS configuration for the host defined at `ingress.hostname` parameter
   210    ## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
   211    ## You can:
   212    ##   - Use the `ingress.secrets` parameter to create this TLS secret
   213    ##   - Rely on cert-manager to create it by setting the corresponding annotations
   214    ##   - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
   215    ##
   216    tls: false
   217    ## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
   218    ##
   219    selfSigned: false
   220    ## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record
   221    ## e.g:
   222    ## extraHosts:
   223    ##   - name: clickhouse.local
   224    ##     path: /
   225    ##
   226    extraHosts: []
   227    ## @param ingress.extraPaths An array with additional arbitrary paths that may need to be added to the ingress under the main host
   228    ## e.g:
   229    ## extraPaths:
   230    ## - path: /*
   231    ##   backend:
   232    ##     serviceName: ssl-redirect
   233    ##     servicePort: use-annotation
   234    ##
   235    extraPaths: []
   236    ## @param ingress.extraTls TLS configuration for additional hostname(s) to be covered with this ingress record
   237    ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
   238    ## e.g:
   239    ## extraTls:
   240    ## - hosts:
   241    ##     - clickhouse.local
   242    ##   secretName: clickhouse.local-tls
   243    ##
   244    extraTls: []
   245    ## @param ingress.secrets Custom TLS certificates as secrets
   246    ## NOTE: 'key' and 'certificate' are expected in PEM format
   247    ## NOTE: 'name' should line up with a 'secretName' set further up
   248    ## If it is not set and you're using cert-manager, this is unneeded, as it will create a secret for you with valid certificates
   249    ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days
   250    ## It is also possible to create and manage the certificates outside of this helm chart
   251    ## Please see README.md for more information
   252    ## e.g:
   253    ## secrets:
   254    ##   - name: clickhouse.local-tls
   255    ##     key: |-
   256    ##       -----BEGIN RSA PRIVATE KEY-----
   257    ##       ...
   258    ##       -----END RSA PRIVATE KEY-----
   259    ##     certificate: |-
   260    ##       -----BEGIN CERTIFICATE-----
   261    ##       ...
   262    ##       -----END CERTIFICATE-----
   263    ##
   264    secrets: []
   265    ## @param ingress.extraRules Additional rules to be covered with this ingress record
   266    ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules
   267    ## e.g:
   268    ## extraRules:
   269    ## - host: example.local
   270    ##     http:
   271    ##       path: /
   272    ##       backend:
   273    ##         service:
   274    ##           name: example-svc
   275    ##           port:
   276    ##             name: http
   277    ##
   278    extraRules: []
   279  
   280  nameOverride: ""
   281  fullnameOverride: ""
   282  
   283  # The RBAC permission used by cluster component pod, now include event.create
   284  serviceAccount:
   285    name: ""