Files
charts/bitnami/clickhouse-operator/templates/NOTES.txt
Juan Ariza Toledano 4c1954526f [bitnami/clickhouse-operator] feat: new chart (#32816)
* [bitnami/clickhouse-operator] feat: new chart

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* Update CHANGELOG.md

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

* chore: add VIB skeleton

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* feat: add parameters to customize config.d and users.d

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

* docs: document missing README sections

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* Update CHANGELOG.md

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

* feat: vib runtime parameters

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* bugfix: simplify keeper installation

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* feat: vib with security context

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* Update CHANGELOG.md

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

* doc: update example in README

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* ci: use BITNAMI_DEBUG, helpful if deployment fails

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* feat: add suggestions from code review

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* ci: fix expected data permissions

Signed-off-by: juan131 <juan.ariza@broadcom.com>

* bugfix: typos

Signed-off-by: juan131 <juan.ariza@broadcom.com>

---------

Signed-off-by: juan131 <juan.ariza@broadcom.com>
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
Co-authored-by: Bitnami Bot <bitnami.bot@broadcom.com>
2025-04-08 14:46:36 +00:00

40 lines
2.1 KiB
Plaintext

CHART NAME: {{ .Chart.Name }}
CHART VERSION: {{ .Chart.Version }}
APP VERSION: {{ .Chart.AppVersion }}
Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami for more information.
** Please be patient while the chart is being deployed **
Check the status of the pods by running this command:
kubectl get pods --namespace {{ include "common.names.namespace" . | quote }} -l app.kubernetes.io/instance={{ .Release.Name }}
Check the ClickHouse Operator documentation for instructions on how to deploy a ClickHouse cluster:
https://docs.altinity.com/altinitykubernetesoperator/kubernetesquickstartguide/quickcluster
{{- if .Values.rbac.create }}
{{- if .Values.watchAllNamespaces }}
WARNING: ClickHouse Operator can access all secrets in the cluster. This could pose a security risk if the application gets compromised.
You can limit allowed namespaces by setting watchAllNamespaces = false and configuring watchNamespaces
{{- else }}
ClickHouse Operator can ONLY access resources in the following namespaces:
{{ $namespaces := .Values.watchNamespaces | default (list (include "common.names.namespace" .)) }}
{{- range $namespace := $namespaces }}
- {{ $namespace }}
{{- end }}
ClickHouse Operator won't be able to access resources in other namespaces. You can configure this behavior by setting watchNamespaces
{{- end }}
{{- end }}
{{- include "clickhouse-operator.checkRollingTags" . }}
{{- include "clickhouse-operator.validateValues" . }}
{{- include "common.warnings.resources" (dict "sections" (list "" "metrics") "context" $) }}
{{- include "common.warnings.modifiedImages" (dict "images" (list .Values.image .Values.clickHouseImage .Values.keeperImage .Values.metrics.image) "context" $) }}
{{- include "common.errors.insecureImages" (dict "images" (list .Values.image .Values.clickHouseImage .Values.keeperImage .Values.metrics.image) "context" $) }}