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
Currently etcd is hardcoded as topo-implementation in the helm chart Line 102
It would be nice to have that determined by a value from values.yaml, since zookeeper and consul are supported as well.
Use Case(s)
Users wouldn't have to rewrite/fork the helm chart in order to use a different topo-implementation on their Kubernetes cluster.
The text was updated successfully, but these errors were encountered:
Be aware that there is also work in #5703 to add Kubernetes as a topo. I expect that after this is added, it will eventually become the default as it simplifies installs.
Feature Description
Currently etcd is hardcoded as topo-implementation in the helm chart Line 102
It would be nice to have that determined by a value from values.yaml, since zookeeper and consul are supported as well.
Use Case(s)
Users wouldn't have to rewrite/fork the helm chart in order to use a different topo-implementation on their Kubernetes cluster.
The text was updated successfully, but these errors were encountered: