Alex Zhang

@mkocsis-tg Would you like to add some descriptions of the PR content.

Did you create a route to proxy for the Dashboard?

@youngwookim Could you provide the reproduce steps? Also, it seems that the ETCD data was corrupted, the member id is invalid.

@youngwookim Strange, could you try to roll back this upgrade and see whether the ETCD cluster recoveries from this fault? Also, we may have to get insight into the ETCD...

> @tokers > > Rollback to 0.4.0 chart: > > ``` > $ helm list -n apisix > NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION > apisix apisix 2...

How many instances are in your ETCD cluster? maybe we can backup the data from the healthy node and use it in the bad one.

Basically, you only need to use the apisix (or its ingress controller and dashboard) images when you want to deploy it to ARM env.

Others are not related to the architecture.

@ajistyle If you create a TLS type Kubernetes Secret object, the perspective keys are "tls.crt" and "tls.key", so you should use the correct keys in settings `etcd.auth.tls.certFilename` and `etcd.auth.tls.certKeyFilename`. What's...

> kubectl create secret tls etcd-ssl-s -n ops \ --cert=/opt/zhuji/helm/apisix/cert/etcd.crt \ --key=/opt/zhuji/helm/apisix/cert/etcd-key.key \ --dry-run -o yaml > etcd-ssl-s.yaml The key names of tls type secret will be "tls.crt", "tls.key", but...