github.com/1aal/kubeblocks@v0.0.0-20231107070852-e1c03e598921/deploy/etcd-cluster/values.yaml (about) 1 ## @param terminationPolicy define Cluster termination policy. One of DoNotTerminate, Halt, Delete, WipeOut. 2 ## 3 terminationPolicy: Halt 4 5 ## Monitoring configurations 6 monitor: 7 ## @param monitor.enabled if `true`, enable Cluster monitor capabilities 8 ## 9 enabled: false 10 11 ## Service configurations 12 ## 13 service: 14 ## @param service.type etcd service type, valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. 15 ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types 16 ## 17 type: ClusterIP 18 19 clusterVersionOverride: "" 20 nameOverride: "" 21 fullnameOverride: "" 22 23 ## @param tolerations define global Tolerations for the cluster all pod's assignment 24 ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ 25 ## 26 tolerations: [] 27 28 29 ## @param topologySpreadConstraints Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template 30 ## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#spread-constraints-for-pods 31 ## 32 topologyKeys: 33 - kubernetes.io/hostname 34 35 36 ## @param affinity is affinity setting for etcd cluster pods assignment 37 ## 38 affinity: {} 39 40 replicaCount: 3 41 42 resources: { } 43 # We usually recommend not to specify default resources and to leave this as a conscious 44 # choice for the user. This also increases chances charts run on environments with little 45 # resources, such as Minikube. If you do want to specify resources, uncomment the following 46 # lines, adjust them as necessary, and remove the curly braces after 'resources:'. 47 # limits: 48 # cpu: 100m 49 # memory: 128Mi 50 # requests: 51 # cpu: 100m 52 # memory: 128Mi 53 54 ## Enable persistence using Persistent Volume Claims 55 ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/ 56 ## 57 persistence: 58 ## @param shard[*].persistence.enabled Enable persistence using Persistent Volume Claims 59 ## 60 enabled: true 61 ## `data` volume settings 62 ## 63 data: 64 ## @param shard[*].persistence.data.storageClassName Storage class of backing PVC 65 ## If defined, storageClassName: <storageClass> 66 ## If set to "-", storageClassName: "", which disables dynamic provisioning 67 ## If undefined (the default) or set to null, no storageClassName spec is 68 ## set, choosing the default provisioner. (gp2 on AWS, standard on 69 ## GKE, AWS & OpenStack) 70 ## 71 storageClassName: 72 ## @param shard[*].persistence.size Size of data volume 73 ## 74 size: 1Gi 75 76 ingress: 77 ## @param ingress.enabled Enable ingress record generation for etcd 78 ## 79 enabled: false 80 ## @param ingress.pathType Ingress path type 81 ## 82 pathType: ImplementationSpecific 83 ## @param ingress.apiVersion Force Ingress API version (automatically detected if not set) 84 ## 85 apiVersion: "" 86 ## @param ingress.hostname Default host for the ingress record 87 ## 88 hostname: etcd.local 89 ## @param ingress.ingressClassName IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) 90 ## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster . 91 ## ref: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/ 92 ## 93 ingressClassName: "" 94 ## @param ingress.path Default path for the ingress record 95 ## NOTE: You may need to set this to '/*' in order to use this with ALB ingress controllers 96 ## 97 path: / 98 ## @param ingress.annotations Additional annotations for the Ingress resource. To enable certificate auto generation, place here your cert-manager annotations. 99 ## Use this parameter to set the required annotations for cert-manager, see 100 ## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations 101 ## e.g: 102 ## annotations: 103 ## kubernetes.io/ingress.class: nginx 104 ## cert-manager.io/cluster-issuer: cluster-issuer-name 105 ## 106 annotations: {} 107 ## @param ingress.tls Enable TLS configuration for the host defined at `ingress.hostname` parameter 108 ## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}` 109 ## You can: 110 ## - Use the `ingress.secrets` parameter to create this TLS secret 111 ## - Rely on cert-manager to create it by setting the corresponding annotations 112 ## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true` 113 ## 114 tls: false 115 ## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm 116 ## 117 selfSigned: false 118 ## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record 119 ## e.g: 120 ## extraHosts: 121 ## - name: etcd.local 122 ## path: / 123 ## 124 extraHosts: [] 125 ## @param ingress.extraPaths An array with additional arbitrary paths that may need to be added to the ingress under the main host 126 ## e.g: 127 ## extraPaths: 128 ## - path: /* 129 ## backend: 130 ## serviceName: ssl-redirect 131 ## servicePort: use-annotation 132 ## 133 extraPaths: [] 134 ## @param ingress.extraTls TLS configuration for additional hostname(s) to be covered with this ingress record 135 ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls 136 ## e.g: 137 ## extraTls: 138 ## - hosts: 139 ## - etcd.local 140 ## secretName: etcd.local-tls 141 ## 142 extraTls: [] 143 ## @param ingress.secrets Custom TLS certificates as secrets 144 ## NOTE: 'key' and 'certificate' are expected in PEM format 145 ## NOTE: 'name' should line up with a 'secretName' set further up 146 ## 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 147 ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days 148 ## It is also possible to create and manage the certificates outside of this helm chart 149 ## Please see README.md for more information 150 ## e.g: 151 ## secrets: 152 ## - name: etcd.local-tls 153 ## key: |- 154 ## -----BEGIN RSA PRIVATE KEY----- 155 ## ... 156 ## -----END RSA PRIVATE KEY----- 157 ## certificate: |- 158 ## -----BEGIN CERTIFICATE----- 159 ## ... 160 ## -----END CERTIFICATE----- 161 ## 162 secrets: [] 163 ## @param ingress.extraRules Additional rules to be covered with this ingress record 164 ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules 165 ## e.g: 166 ## extraRules: 167 ## - host: example.local 168 ## http: 169 ## path: / 170 ## backend: 171 ## service: 172 ## name: example-svc 173 ## port: 174 ## name: http 175 ## 176 extraRules: [] 177 178 # The RBAC permission used by cluster component pod, now include event.create 179 serviceAccount: 180 name: ""