Alex Zhang
cc @bzp2010
You cannot tweak the shared memory size and reload APISIX. This is due to the Nginx limitation. The way to change the size is "hot reload" APISIX, but it's not...
Wait, how did you execute the reload? In Kubernetes, we don't use "reload" but just create new pods to replace old ones.
See https://github.com/apache/apisix-helm-chart/issues/11.
Yes, the TLS support is not exposed via the Helm Chart. Would you like to submit a PR to support it? Thanks!
> > @Lyt99 If you are using deployment that do not use hostnetwork option, and wanna place each apisix instances on different nodes, then you should configure the `apisix.affinity` options....
@xzycn I think this issue is not related to APISIX. It's totally an ETCD operation skill. Try to find help from ETCD community.
Make sense.
We need a way to fetch the secret data to the container, either from volume or environment variables. Let's leave it here and see others' ideas.
I think this is a how-to problem about helm, see https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing.