Alex Zhang

> by default using the currently selected kubectl/release namespace You mean the namespace that when users run the `helm` command?

> So, PR is now updated: > > * Ingress > Ingress chart can now be installed in the same namespace as the admin service without having to pass `--set`...

Is anything special for this ServiceAccount? I don't see the role binding for it.

> @tokers Is is better if we specify the cluster role rules in `values.yaml`? Like so:  And use `.serviceAccount.create` as the only flag to determine whether to create cluster...

You should use the latest APISIX image (such as `2.10.2`) so that the mTLS features are supported.

The key prefix configuration item has not exposed yet, welcome to submit a PR to enable it!

I think this problem is not relevant to the APISIX, according to the error log, it's caused by the neworking issue, could you troubleshoot it firstly?

> I think this problem is not relevant to the APISIX, according to the error log, it's caused by the neworking issue, could you troubleshoot it firstly? Also, please provide...

It seems APISIX doens't use the resolver in `/etc/resolv.conf`. Could you please paste the nginx.conf in your APISIX container?

> # way to install > ```shell > git clone https://github.com/apache/apisix-helm-chart.git > cd apisix-helm-chart/charts/apisix > helm dependency update . > helm install apisix . --set gateway.type=NodePort --set allow.ipList="{0.0.0.0/0}" --namespace ingress-apisix...