lpiob commented on issue #487: URL: https://github.com/apache/apisix-helm-chart/issues/487#issuecomment-1455066100
I was unable to recreate the issue by installing and then upgrading the apisix helm chart. I was able to reproduce the issue if any of the pods was recreated after the installation, but before helm upgrade. The pod came back with a setting to form a new cluster and couldn't do so, even after updating the initialClusterState to existing. The setting and it's value is defined within the [bitnami etcd helm chart](https://github.com/bitnami/charts/blob/430394a7972a92a183f7f19cb5db35d6d85c8cdb/bitnami/etcd/values.yaml#L198-L203) (not: apisix helm chart). Do you have any idea how to fix that behavior? I can't thing of anything else than 1) warning Apisix users to perform helm install and then upgrade before using the service or 2) delegating the issue to upstream (bitnami) so they compute the value outside of the chart. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
