## @section Global parameters ## Global Docker image parameters ## Please, note that this will override the image parameters, including dependencies, configured to use the global value ## Current available global Docker image parameters: imageRegistry, imagePullSecrets and storageClass ## ## @param global.imageRegistry Global Docker image registry ## @param global.imagePullSecrets Global Docker registry secret names as an array ## @param global.storageClass Global StorageClass for Persistent Volume(s) ## global: imageRegistry: "" ## E.g. ## imagePullSecrets: ## - myRegistryKeySecretName ## imagePullSecrets: [] storageClass: "openebs-hostpath" ## @section Common parameters ## ## @param kubeVersion Override Kubernetes version ## kubeVersion: "" ## @param nameOverride String to partially override common.names.fullname template (will maintain the release name) ## nameOverride: "" ## @param fullnameOverride String to fully override common.names.fullname template ## fullnameOverride: "" ## @param commonLabels Labels to add to all deployed resources ## commonLabels: {} ## @param commonAnnotations Annotations to add to all deployed resources ## commonAnnotations: {} ## @param clusterDomain Kubernetes Cluster Domain ## clusterDomain: cluster.local ## @param extraDeploy Array of extra objects to deploy with the release ## extraDeploy: [] ## Enable diagnostic mode in the deployment ## diagnosticMode: ## @param diagnosticMode.enabled Enable diagnostic mode (all probes will be disabled and the command will be overridden) ## enabled: false ## @param diagnosticMode.command Command to override all containers in the deployment ## command: - sleep ## @param diagnosticMode.args Args to override all containers in the deployment ## args: - infinity ## @section Halo Image parameters ## ## Halo image ## ref: https://hub.docker.com/r/bitnami/halo/tags/ ## @param image.registry Halo image registry ## @param image.repository Halo image repository ## @param image.tag Halo image tag (immutable tags are recommended) ## @param image.digest Halo image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag ## @param image.pullPolicy Halo image pull policy ## @param image.pullSecrets Halo image pull secrets ## image: registry: docker.io repository: halohub/halo tag: 2.11.2 digest: "" ## Specify a imagePullPolicy ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent' ## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images ## pullPolicy: IfNotPresent ## Optionally specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ ## e.g: ## pullSecrets: ## - myRegistryKeySecretName ## pullSecrets: [] ## @section Halo Configuration parameters ## Halo settings based on environment variables ## ref: https://github.com/bitnami/containers/tree/main/bitnami/halo#environment-variables ## ## @param haloUsername Halo username ## haloUsername: admin ## @param haloPassword Halo user password ## Defaults to a random 10-character alphanumeric string if not set ## haloPassword: "halocecf@" ## @param existingSecret Name of existing secret containing Halo credentials ## NOTE: Must contain key `halo-password` ## NOTE: When it's set, the `haloPassword` parameter is ignored ## existingSecret: "" ## @param haloExternalUrl 外部访问地址，请根据实际需要修改 ## haloExternalUrl: "http://halo.cestong.com.cn" ## @param haloScheme Scheme to use to generate Halo URLs ## haloScheme: http ## @param command Override default container command (useful when using custom images) ## command: [] ## @param args Override default container args (useful when using custom images) ## args: [] ## @param extraEnvVars Array with extra environment variables to add to the Halo container ## e.g: ## extraEnvVars: ## - name: FOO ## value: "bar" ## extraEnvVars: [] ## @param extraEnvVarsCM Name of existing ConfigMap containing extra env vars ## extraEnvVarsCM: "" ## @param extraEnvVarsSecret Name of existing Secret containing extra env vars ## extraEnvVarsSecret: "" ## @section Database Parameters ## ## PostgreSQL chart configuration ## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml ## postgresql: ## @param postgresql.enabled Deploy a PostgreSQL server to satisfy the applications database requirements ## To use an external database set this to false and configure the `externalDatabase.*` parameters ## enabled: false ## @param postgresql.architecture PostgreSQL architecture. Allowed values: `standalone` or `replication` ## architecture: standalone ## PostgreSQL Authentication parameters ## @param postgresql.auth.rootPassword PostgreSQL root password ## @param postgresql.auth.database PostgreSQL custom database ## @param postgresql.auth.username PostgreSQL custom user name ## @param postgresql.auth.password PostgreSQL custom user password ## ref: https://github.com/bitnami/containers/tree/main/bitnami/postgresql#setting-the-root-password-on-first-run ## https://github.com/bitnami/containers/blob/main/bitnami/postgresql/README.md#creating-a-database-on-first-run ## https://github.com/bitnami/containers/blob/main/bitnami/postgresql/README.md#creating-a-database-user-on-first-run ## auth: rootPassword: "" database: halo username: halo password: "" ## PostgreSQL Primary configuration ## primary: ## PostgreSQL Primary Persistence parameters ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/ ## @param postgresql.primary.persistence.enabled Enable persistence on PostgreSQL using PVC(s) ## @param postgresql.primary.persistence.storageClass Persistent Volume storage class ## @param postgresql.primary.persistence.accessModes [array] Persistent Volume access modes ## @param postgresql.primary.persistence.size Persistent Volume size ## persistence: enabled: true storageClass: "" accessModes: - ReadWriteOnce size: 8Gi ## MySQL chart configuration ## ref: https://github.com/bitnami/charts/blob/main/bitnami/mysql/values.yaml ## mysql: ## @param mysql.enabled Deploy a MySQL server to satisfy the applications database requirements ## To use an external database set this to false and configure the `externalDatabase.*` parameters ## enabled: false ## @param mysql.architecture MySQL architecture. Allowed values: `standalone` or `replication` ## architecture: standalone ## MySQL Authentication parameters ## @param mysql.auth.rootPassword MySQL root password ## @param mysql.auth.database MySQL custom database ## @param mysql.auth.username MySQL custom user name ## @param mysql.auth.password MySQL custom user password ## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-the-root-password-on-first-run ## https://github.com/bitnami/containers/blob/main/bitnami/mysql/README.md#creating-a-database-on-first-run ## https://github.com/bitnami/containers/blob/main/bitnami/mysql/README.md#creating-a-database-user-on-first-run ## auth: rootPassword: "" database: halo username: halo password: "" ## MySQL Primary configuration ## primary: ## MySQL Primary Persistence parameters ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/ ## @param mysql.primary.persistence.enabled Enable persistence on MySQL using PVC(s) ## @param mysql.primary.persistence.storageClass Persistent Volume storage class ## @param mysql.primary.persistence.accessModes [array] Persistent Volume access modes ## @param mysql.primary.persistence.size Persistent Volume size ## persistence: enabled: true storageClass: "" accessModes: - ReadWriteOnce size: 8Gi ## External Database Configuration ## All of these values are only used if `postgresql.enabled=false` ## externalDatabase: ## @param externalDatabase.platform External Database platform ## platform: mysql ## @param externalDatabase.host External Database server host ## host: "mysql-primary.observe.svc.cluster.local" ## @param externalDatabase.port External Database server port ## port: "3306" ## @param externalDatabase.user External Database username ## user: "halo" ## @param externalDatabase.password External Database user password ## password: "halo@cestong.com" ## @param externalDatabase.database External Database database name ## database: "halo" ## @param externalDatabase.existingSecret The name of an existing secret with database credentials. Evaluated as a template ## NOTE: Must contain key `password` ## NOTE: When it's set, the `externalDatabase.password` parameter is ignored ## existingSecret: "" ## @section Halo deployment parameters ## ## @param replicaCount Number of Halo replicas to deploy ## NOTE: ReadWriteMany PVC(s) are required if replicaCount > 1 ## replicaCount: 1 ## @param updateStrategy.type Halo deployment strategy type ## @param updateStrategy.rollingUpdate Halo deployment rolling update configuration parameters ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy ## NOTE: Set it to `Recreate` if you use a PV that cannot be mounted on multiple pods ## e.g: ## updateStrategy: ## type: RollingUpdate ## rollingUpdate: ## maxSurge: 25% ## maxUnavailable: 25% ## updateStrategy: type: RollingUpdate rollingUpdate: {} ## @param schedulerName Alternate scheduler ## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/ ## schedulerName: "" ## @param topologySpreadConstraints Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template ## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#spread-constraints-for-pods ## topologySpreadConstraints: [] ## @param priorityClassName Name of the existing priority class to be used by Halo pods, priority class needs to be created beforehand ## Ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/ ## priorityClassName: "" ## @param hostAliases [array] Halo pod host aliases ## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/ ## hostAliases: ## Required for Apache exporter to work ## - ip: "127.0.0.1" hostnames: - "status.localhost" ## @param extraVolumes Optionally specify extra list of additional volumes for Halo pods ## extraVolumes: [] ## @param extraVolumeMounts Optionally specify extra list of additional volumeMounts for Halo container(s) ## extraVolumeMounts: [] ## @param sidecars Add additional sidecar containers to the Halo pod ## e.g: ## sidecars: ## - name: your-image-name ## image: your-image ## imagePullPolicy: Always ## ports: ## - name: portname ## containerPort: 1234 ## sidecars: [] ## @param initContainers Add additional init containers to the Halo pods ## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ ## e.g: ## initContainers: ## - name: your-image-name ## image: your-image ## imagePullPolicy: Always ## command: ['sh', '-c', 'copy themes and plugins from git and push to /bitnami/halo/wp-content. Should work with extraVolumeMounts and extraVolumes'] ## initContainers: [] ## @param podLabels Extra labels for Halo pods ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ ## podLabels: {} ## @param podAnnotations Annotations for Halo pods ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ ## podAnnotations: {} ## @param podAffinityPreset Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` ## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity ## podAffinityPreset: "" ## @param podAntiAffinityPreset Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` ## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity ## podAntiAffinityPreset: soft ## Node affinity preset ## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity ## nodeAffinityPreset: ## @param nodeAffinityPreset.type Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` ## type: "" ## @param nodeAffinityPreset.key Node label key to match. Ignored if `affinity` is set ## key: "" ## @param nodeAffinityPreset.values Node label values to match. Ignored if `affinity` is set ## E.g. ## values: ## - e2e-az1 ## - e2e-az2 ## values: [] ## @param affinity Affinity for pod assignment ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity ## NOTE: podAffinityPreset, podAntiAffinityPreset, and nodeAffinityPreset will be ignored when it's set ## affinity: {} ## @param nodeSelector Node labels for pod assignment ## ref: https://kubernetes.io/docs/user-guide/node-selection/ ## nodeSelector: {} ## @param tolerations Tolerations for pod assignment ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ ## tolerations: [] ## Halo containers' resource requests and limits ## ref: https://kubernetes.io/docs/user-guide/compute-resources/ ## @param resources.limits The resources limits for the Halo containers ## @param resources.requests.memory The requested memory for the Halo containers ## @param resources.requests.cpu The requested cpu for the Halo containers ## resources: limits: {} requests: memory: 4096Mi cpu: 1 ## Container ports ## @param containerPorts.http Halo HTTP container port ## containerPorts: http: 8090 ## @param extraContainerPorts Optionally specify extra list of additional ports for Halo container(s) ## e.g: ## extraContainerPorts: ## - name: myservice ## containerPort: 9090 ## extraContainerPorts: [] ## Configure Pods Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod ## @param podSecurityContext.enabled Enabled Halo pods' Security Context ## @param podSecurityContext.fsGroup Set Halo pod's Security Context fsGroup ## podSecurityContext: enabled: true fsGroup: 1001 ## Configure Container Security Context (only main container) ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container ## @param containerSecurityContext.enabled Enabled Halo containers' Security Context ## @param containerSecurityContext.runAsUser Set Halo container's Security Context runAsUser ## @param containerSecurityContext.runAsNonRoot Set Halo container's Security Context runAsNonRoot ## @param containerSecurityContext.allowPrivilegeEscalation Set Halo container's privilege escalation ## @param containerSecurityContext.capabilities.drop Set Halo container's Security Context runAsNonRoot ## containerSecurityContext: enabled: true runAsUser: 1001 runAsNonRoot: true allowPrivilegeEscalation: false capabilities: drop: ["ALL"] ## Configure extra options for Halo containers' liveness, readiness and startup probes ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes ## @param livenessProbe.enabled Enable livenessProbe on Halo containers ## @skip livenessProbe.httpGet ## @param livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe ## @param livenessProbe.periodSeconds Period seconds for livenessProbe ## @param livenessProbe.timeoutSeconds Timeout seconds for livenessProbe ## @param livenessProbe.failureThreshold Failure threshold for livenessProbe ## @param livenessProbe.successThreshold Success threshold for livenessProbe ## livenessProbe: enabled: true httpGet: path: / port: "{{ .Values.haloScheme }}" scheme: "{{ .Values.haloScheme | upper }}" ## If using an HTTPS-terminating load-balancer, the probes may need to behave ## like the balancer to prevent HTTP 302 responses. According to the Kubernetes ## docs, 302 should be considered "successful", but this issue on GitHub ## (https://github.com/kubernetes/kubernetes/issues/47893) shows that it isn't. ## E.g. ## httpHeaders: ## - name: X-Forwarded-Proto ## value: https ## httpHeaders: [] initialDelaySeconds: 30 periodSeconds: 10 timeoutSeconds: 5 failureThreshold: 3 successThreshold: 1 ## @param readinessProbe.enabled Enable readinessProbe on Halo containers ## @skip readinessProbe.httpGet ## @param readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe ## @param readinessProbe.periodSeconds Period seconds for readinessProbe ## @param readinessProbe.timeoutSeconds Timeout seconds for readinessProbe ## @param readinessProbe.failureThreshold Failure threshold for readinessProbe ## @param readinessProbe.successThreshold Success threshold for readinessProbe ## readinessProbe: enabled: true httpGet: path: / port: "{{ .Values.haloScheme }}" scheme: "{{ .Values.haloScheme | upper }}" ## If using an HTTPS-terminating load-balancer, the probes may need to behave ## like the balancer to prevent HTTP 302 responses. According to the Kubernetes ## docs, 302 should be considered "successful", but this issue on GitHub ## (https://github.com/kubernetes/kubernetes/issues/47893) shows that it isn't. ## E.g. ## httpHeaders: ## - name: X-Forwarded-Proto ## value: https ## httpHeaders: [] initialDelaySeconds: 30 periodSeconds: 10 timeoutSeconds: 5 failureThreshold: 3 successThreshold: 1 ## @param startupProbe.enabled Enable startupProbe on Halo containers ## @skip startupProbe.httpGet ## @param startupProbe.initialDelaySeconds Initial delay seconds for startupProbe ## @param startupProbe.periodSeconds Period seconds for startupProbe ## @param startupProbe.timeoutSeconds Timeout seconds for startupProbe ## @param startupProbe.failureThreshold Failure threshold for startupProbe ## @param startupProbe.successThreshold Success threshold for startupProbe ## startupProbe: enabled: false httpGet: path: / port: "{{ .Values.haloScheme }}" scheme: "{{ .Values.haloScheme | upper }}" ## If using an HTTPS-terminating load-balancer, the probes may need to behave ## like the balancer to prevent HTTP 302 responses. According to the Kubernetes ## docs, 302 should be considered "successful", but this issue on GitHub ## (https://github.com/kubernetes/kubernetes/issues/47893) shows that it isn't. ## E.g. ## httpHeaders: ## - name: X-Forwarded-Proto ## value: https ## httpHeaders: [] initialDelaySeconds: 10 periodSeconds: 5 timeoutSeconds: 3 failureThreshold: 3 successThreshold: 1 ## @param customLivenessProbe Custom livenessProbe that overrides the default one ## customLivenessProbe: {} ## @param customReadinessProbe Custom readinessProbe that overrides the default one ## customReadinessProbe: {} ## @param customStartupProbe Custom startupProbe that overrides the default one ## customStartupProbe: {} ## @param lifecycleHooks for the Halo container(s) to automate configuration before or after startup ## lifecycleHooks: {} ## @section Traffic Exposure Parameters ## ## Halo service parameters ## service: ## @param service.type Halo service type ## type: NodePort ## @param service.ports.http Halo service HTTP port ## ports: http: 80 ## Node ports to expose ## @param service.nodePorts.http Node port for HTTP ## NOTE: choose port between <30000-32767> ## nodePorts: http: "" ## @param service.sessionAffinity Control where client requests go, to the same pod or round-robin ## Values: ClientIP or None ## ref: https://kubernetes.io/docs/user-guide/services/ ## sessionAffinity: None ## @param service.sessionAffinityConfig Additional settings for the sessionAffinity ## sessionAffinityConfig: ## clientIP: ## timeoutSeconds: 300 ## sessionAffinityConfig: {} ## @param service.clusterIP Halo service Cluster IP ## e.g.: ## clusterIP: None ## clusterIP: "" ## @param service.loadBalancerIP Halo service Load Balancer IP ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer ## loadBalancerIP: "" ## @param service.loadBalancerSourceRanges Halo service Load Balancer sources ## ref: https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service ## e.g: ## loadBalancerSourceRanges: ## - 10.10.10.0/24 ## loadBalancerSourceRanges: [] ## @param service.externalTrafficPolicy Halo service external traffic policy ## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip ## externalTrafficPolicy: Cluster ## @param service.annotations Additional custom annotations for Halo service ## annotations: {} ## @param service.extraPorts Extra port to expose on Halo service ## extraPorts: [] ## Configure the ingress resource that allows you to access the Halo installation ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/ ## ingress: ## @param ingress.enabled Enable ingress record generation for Halo ## enabled: false ## @param ingress.pathType Ingress path type ## pathType: ImplementationSpecific ## @param ingress.apiVersion Force Ingress API version (automatically detected if not set) ## apiVersion: "" ## @param ingress.ingressClassName IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) ## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster . ## ref: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/ ## ingressClassName: "nginx" ## @param ingress.hostname Default host for the ingress record ## hostname: halo.cestong.com.cn ## @param ingress.path Default path for the ingress record ## NOTE: You may need to set this to '/*' in order to use this with ALB ingress controllers ## path: / ## @param ingress.annotations Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations. ## For a full list of possible ingress annotations, please see ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md ## Use this parameter to set the required annotations for cert-manager, see ## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations ## ## e.g: ## annotations: ## kubernetes.io/ingress.class: nginx ## cert-manager.io/cluster-issuer: cluster-issuer-name ## annotations: {} ## @param ingress.tls Enable TLS configuration for the host defined at `ingress.hostname` parameter ## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}` ## You can: ## - Use the `ingress.secrets` parameter to create this TLS secret ## - Rely on cert-manager to create it by setting the corresponding annotations ## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true` ## tls: false ## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm ## selfSigned: false ## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record ## e.g: ## extraHosts: ## - name: halo.local ## path: / ## extraHosts: [] ## @param ingress.extraPaths An array with additional arbitrary paths that may need to be added to the ingress under the main host ## e.g: ## extraPaths: ## - path: /* ## backend: ## serviceName: ssl-redirect ## servicePort: use-annotation ## extraPaths: [] ## @param ingress.extraTls TLS configuration for additional hostname(s) to be covered with this ingress record ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls ## e.g: ## extraTls: ## - hosts: ## - halo.local ## secretName: halo.local-tls ## extraTls: [] ## @param ingress.secrets Custom TLS certificates as secrets ## NOTE: 'key' and 'certificate' are expected in PEM format ## NOTE: 'name' should line up with a 'secretName' set further up ## 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 ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days ## It is also possible to create and manage the certificates outside of this helm chart ## Please see README.md for more information ## e.g: ## secrets: ## - name: halo.local-tls ## key: |- ## -----BEGIN RSA PRIVATE KEY----- ## ... ## -----END RSA PRIVATE KEY----- ## certificate: |- ## -----BEGIN CERTIFICATE----- ## ... ## -----END CERTIFICATE----- ## secrets: [] ## @param ingress.extraRules Additional rules to be covered with this ingress record ## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules ## e.g: ## extraRules: ## - host: halo.local ## http: ## path: / ## backend: ## service: ## name: halo-svc ## port: ## name: http ## extraRules: [] ## @section Persistence Parameters ## ## Persistence Parameters ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/ ## persistence: ## @param persistence.enabled Enable persistence using Persistent Volume Claims ## enabled: true ## @param persistence.storageClass Persistent Volume storage class ## If defined, storageClassName: ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default) or set to null, no storageClassName spec is set, choosing the default provisioner ## storageClass: "" ## @param persistence.accessModes [array] Persistent Volume access modes ## accessModes: - ReadWriteOnce ## @param persistence.size Persistent Volume size ## size: 10Gi ## @param persistence.dataSource Custom PVC data source ## dataSource: {} ## @param persistence.existingClaim The name of an existing PVC to use for persistence ## existingClaim: "" ## @param persistence.selector Selector to match an existing Persistent Volume for Halo data PVC ## If set, the PVC can't have a PV dynamically provisioned for it ## E.g. ## selector: ## matchLabels: ## app: my-app ## selector: {} ## @param persistence.annotations Persistent Volume Claim annotations ## annotations: {} ## Init containers parameters: ## volumePermissions: Change the owner and group of the persistent volume(s) mountpoint(s) to 'runAsUser:fsGroup' on each node ## volumePermissions: ## @param volumePermissions.enabled Enable init container that changes the owner/group of the PV mount point to `runAsUser:fsGroup` ## enabled: false ## Bitnami Shell image ## ref: https://hub.docker.com/r/bitnami/bitnami-shell/tags/ ## @param volumePermissions.image.registry Bitnami Shell image registry ## @param volumePermissions.image.repository Bitnami Shell image repository ## @param volumePermissions.image.tag Bitnami Shell image tag (immutable tags are recommended) ## @param volumePermissions.image.digest Bitnami Shell image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag ## @param volumePermissions.image.pullPolicy Bitnami Shell image pull policy ## @param volumePermissions.image.pullSecrets Bitnami Shell image pull secrets ## image: registry: docker.io repository: bitnami/bitnami-shell tag: 11-debian-11-r59 digest: "" pullPolicy: IfNotPresent ## Optionally specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ ## e.g: ## pullSecrets: ## - myRegistryKeySecretName ## pullSecrets: [] ## Init container's resource requests and limits ## ref: https://kubernetes.io/docs/user-guide/compute-resources/ ## @param volumePermissions.resources.limits The resources limits for the init container ## @param volumePermissions.resources.requests The requested resources for the init container ## resources: limits: {} requests: {} ## Init container' Security Context ## Note: the chown of the data folder is done to containerSecurityContext.runAsUser ## and not the below volumePermissions.containerSecurityContext.runAsUser ## @param volumePermissions.containerSecurityContext.runAsUser User ID for the init container ## containerSecurityContext: runAsUser: 0 ## @section Other Parameters ## ## Halo Service Account ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/ ## serviceAccount: ## @param serviceAccount.create Enable creation of ServiceAccount for Halo pod ## create: false ## @param serviceAccount.name The name of the ServiceAccount to use. ## If not set and create is true, a name is generated using the common.names.fullname template ## name: "" ## @param serviceAccount.automountServiceAccountToken Allows auto mount of ServiceAccountToken on the serviceAccount created ## Can be set to false if pods using this serviceAccount do not need to use K8s API ## automountServiceAccountToken: true ## @param serviceAccount.annotations Additional custom annotations for the ServiceAccount ## annotations: {} ## @section NetworkPolicy parameters ## ## Add networkpolicies ## networkPolicy: ## @param networkPolicy.enabled Enable network policies ## If ingress.enabled or metrics.enabled are true, configure networkPolicy.ingress and networkPolicy.metrics selectors respectively to allow communication ## enabled: false ## @param networkPolicy.metrics.enabled Enable network policy for metrics (prometheus) ## @param networkPolicy.metrics.namespaceSelector [object] Monitoring namespace selector labels. These labels will be used to identify the prometheus' namespace. ## @param networkPolicy.metrics.podSelector [object] Monitoring pod selector labels. These labels will be used to identify the Prometheus pods. ## metrics: enabled: false ## e.g: ## podSelector: ## label: monitoring ## podSelector: {} ## e.g: ## namespaceSelector: ## label: monitoring ## namespaceSelector: {} ## @param networkPolicy.ingress.enabled Enable network policy for Ingress Proxies ## @param networkPolicy.ingress.namespaceSelector [object] Ingress Proxy namespace selector labels. These labels will be used to identify the Ingress Proxy's namespace. ## @param networkPolicy.ingress.podSelector [object] Ingress Proxy pods selector labels. These labels will be used to identify the Ingress Proxy pods. ## ingress: enabled: false ## e.g: ## podSelector: ## label: ingress ## podSelector: {} ## e.g: ## namespaceSelector: ## label: ingress ## namespaceSelector: {} ## @param networkPolicy.ingressRules.backendOnlyAccessibleByFrontend Enable ingress rule that makes the backend (postgresql) only accessible by testlink's pods. ## @param networkPolicy.ingressRules.customBackendSelector [object] Backend selector labels. These labels will be used to identify the backend pods. ## @param networkPolicy.ingressRules.accessOnlyFrom.enabled Enable ingress rule that makes testlink only accessible from a particular origin ## @param networkPolicy.ingressRules.accessOnlyFrom.namespaceSelector [object] Namespace selector label that is allowed to access testlink. This label will be used to identified the allowed namespace(s). ## @param networkPolicy.ingressRules.accessOnlyFrom.podSelector [object] Pods selector label that is allowed to access testlink. This label will be used to identified the allowed pod(s). ## @param networkPolicy.ingressRules.customRules [object] Custom network policy ingress rule ## ingressRules: ## postgresql backend only can be accessed from testlink ## backendOnlyAccessibleByFrontend: false ## Additional custom backend selector ## e.g: ## customBackendSelector: ## - to: ## - namespaceSelector: ## matchLabels: ## label: example ## customBackendSelector: {} ## Allow only from the indicated: ## accessOnlyFrom: enabled: false ## e.g: ## podSelector: ## label: access ## podSelector: {} ## e.g: ## namespaceSelector: ## label: access ## namespaceSelector: {} ## custom ingress rules ## e.g: ## customRules: ## - from: ## - namespaceSelector: ## matchLabels: ## label: example ## customRules: {} ## @param networkPolicy.egressRules.denyConnectionsToExternal Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53). ## @param networkPolicy.egressRules.customRules [object] Custom network policy rule ## egressRules: # Deny connections to external. This is not compatible with an external database. denyConnectionsToExternal: false ## Additional custom egress rules ## e.g: ## customRules: ## - to: ## - namespaceSelector: ## matchLabels: ## label: example ## customRules: {}