You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Note:** If you installed the Altinity Operator with this chart, your ClickHouse Installations will hang because the Operator will be deleted before their finalizers complete. To resolve this you must manually edit each `chi` resource and remove the finalizer.
50
+
51
+
PVCs created by this helm chart will not be automatically deleted and must be deleted manually. An easy way to do this is to delete the namespace:
52
+
53
+
```sh
54
+
kubectl delete namespace clickhouse
41
55
```
42
56
43
57
> This command removes all the Kubernetes components associated with the chart and deletes the release.
> Use `kubectl port forward` to access your ClickHouse cluster from outside: `kubectl port-forward service clickhouse-eks 9000:9000 & clickhouse-client`
56
70
71
+
## Using Init Scripts with ConfigMap
72
+
73
+
The chart allows mounting a ConfigMap containing initialization scripts that will be executed during the ClickHouse container startup.
74
+
75
+
### How to use:
76
+
77
+
1. Create a ConfigMap containing your initialization scripts:
| clickhouse.defaultUser.allowExternalAccess | bool | `false` | Allow the default user to access ClickHouse from any IP. If set, will override `hostIP` to always be `0.0.0.0/0`. |
| clickhouse.keeper.host | string | `""` | Specify a keeper host. Should be left empty if `clickhouse-keeper.enabled` is `true`. Will override the defaults set from `clickhouse-keeper.enabled`. |
70
127
| clickhouse.keeper.port | int | `2181` | Override the default keeper port |
0 commit comments