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

Feature request

Place the access_log and error_log directives inside the main server block instead of http block.

Feature description

Disable access_log at http block:
File: /etc/nginx/nginx.conf

# ...
http {
    # ...
    access_log off;
    # ...
}
# ...

Enable per site access_log and error_log at main server block:
File: /etc/nginx/

Need to upgrade kind testing to v0.14.0 so we can test against k8s 1.24 releases

https://github.com/kubernetes/ingress-nginx/blob/main/.github/workflows/ci.yaml#L223

/kind feature
/good-first-issue
/priority backlog
/triage accepted

Description

Currently we are using Semantic Pull Requests to check in PR but the project is no longer maintained. we need some alternatives.

e.g.

• https://github.com/amannn/action-semantic-pull-request

If anyone is interested in this, please submit a PR to complete this replacement

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

We have activated the event and post-rollout webhook and canary analysis is skipped so far. However, we never get triggered by the post-rollout webhook. With the event webhook we get this message "Promotion completed! Canary analysis was skipped for my-test-app". But no post-rollout webhook call.

To Reproduce

Our canaries YAML:

apiVersion: flagger.a

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener