Update NGINX and OpenResty to v1.21.4

[rikatz]

As part of the stabilization process, let's update NGINX and Openresty to v1.21.4

/triage accepted
/priority critical-urgent
/area stabilization

[rikatz]

/project stabilization

[k8s-ci-robot]

@rikatz: You must be a member of the kubernetes/ingress-nginx github team to set the project and column.

In response to this:

/project stabilization

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tao12345666333]

let me check it

[tao12345666333]

/assign

[arontsang]

+1 Given that the current version of nginx is flagged by IT as being vulnerable to CVE-2021-23017

[tao12345666333]

I'm working on this 😄

[Kanshiroron]

Is the idea here to upgrade to v1.21.4 as the title suggest (which is already quite old), or to the latest version available v1.23.1?
Because v1.21 security support has expired 2 months ago: https://endoflife.date/nginx and we're looking for a bug fix that has been released on a newer version than v1.21.4.
Thanks

#8856

[tao12345666333]

The current plan is to upgrade to v1.21 as the title, I will submit a PR within this week.

In fact this version is consistent with openrestry

[Kanshiroron]

Thanks @tao12345666333 for your quick answer.
If I understand correctly, the ingress nginx is build on top of OpenRestry, so we'll need to wait for OpenRestry to deliver a version based on the 1.23.1 version of nginx to have a chance to later see it in the ingress nginx right?

[tao12345666333]

right

[tao12345666333]

Open a PR #8889 for this one.
I need some time to finish it ASAP

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tooptoop4]

/remove-lifecycle stale