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
When installing the bitnami/etcd chart with ArgoCD the ETCD_INITIAL_CLUSTER_STATE is never set to existing, because ArgoCD uses helm template to render and install charts.
What do you see instead?
The value of ETCD_INITIAL_CLUSTER_STATE stays at new and new members fail to join the cluster.
The text was updated successfully, but these errors were encountered:
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and want to contribute a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
Name and Version
bitnami/etcd 10.2.18
What architecture are you using?
None
What steps will reproduce the bug?
When installing the
bitnami/etcd
chart with ArgoCD theETCD_INITIAL_CLUSTER_STATE
is never set to existing, because ArgoCD useshelm template
to render and install charts.What do you see instead?
The value of
ETCD_INITIAL_CLUSTER_STATE
stays atnew
and new members fail to join the cluster.The text was updated successfully, but these errors were encountered: