cockroachdb / cockroachdb/helm-charts

Cluster Initialization is missing for custom `conf.join`

Open
#210 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
105
Forks
152
Avg merge
4d 23h
Merged PRs (30d)
5

Description

I have a setup for CockroachDB using multiple Kubernetes Cluster. Since the automatic `join` list only contains the services from the local cluster but not the other cluster, I used a custom `conf.join` list with the services from both clusters. But unfortunately the `job.init` to initialize the cluster is not running for both clusters due to

```yaml
{{ $isClusterInitEnabled := and (eq (len .Values.conf.join) 0) (not (index .Values.conf `single-node`)) }}
{{ $isDatabaseProvisioningEnabled := .Values.init.provisioning.enabled }}
{{- if or $isClusterInitEnabled $isDatabaseProvisioningEnabled }}

````
So I end with an uninitialized database cluster.

What would be the best way to do this? Can we have something like

```yaml
init:
enabled: true
```

to explicitly enable the init on one of the clusters?

Jira issue: HELM-29

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.