nginx

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

For a better overview and transparency we should add column to the supported versions overview table that contains the helm version. That way it is easy to see which helm version includes which nginx ingress version.

/kind documentation

Issue description

比如Nginx自带的响应内容替换库可以替换局部内容：http://nginx.org/en/docs/http/ngx_http_sub_module.html

sub_filter '<a href="http://127.0.0.1:8080/'  '<a href="https://$host/';

比如还有个支持正则替换的库（印象中Openresty已默认支持）：ngx_http_substitutions_filter_module，可以通过正则表达式来替换内容：

subs_filter_types text/html text/css text/xml;
subs_filter st(\d*).example.com $1.example.com ir;
subs_filter a.e

Under edit Proxy Host, it states to use 1.1.1.1/path for sub folder forwarding

1.1.1.1 should not be used like this, as its a valid external address and website

I use naxsi with nginx. I want to add request id which is used by nginx to nginx error logs when blocked by naxsi. Is it possible ? Thanks for help.

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca