Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Downgrade NGINX to v1.19.9 #7635

Closed
rikatz opened this issue Sep 14, 2021 · 4 comments
Closed

Downgrade NGINX to v1.19.9 #7635

rikatz opened this issue Sep 14, 2021 · 4 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
v1.0.1

Comments

@rikatz
Copy link
Contributor

rikatz commented Sep 14, 2021

So during discussion for #7080 and #6896 (#6896 (comment))

We need to downgrade NGINX to v1.19.9, apply the patches for OpenResty and the CVE Patch (for v1.20.1)

/help
/priority critical-urgent
@rikatz rikatz added the kind/bug Categorizes issue or PR as related to a bug. label Sep 14, 2021
@rikatz rikatz added this to the v1.0.1 milestone Sep 14, 2021
@k8s-ci-robot
Copy link
Contributor

@rikatz:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

So during discussion for #7080 and #6896 (#6896 (comment))

We need to downgrade NGINX to v1.19.9, apply the patches for OpenResty and the CVE Patch (for v1.20.1)

/help
/priority critical-urgent

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.

@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Sep 14, 2021
@k8s-ci-robot
Copy link
Contributor

@rikatz: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 14, 2021
@rikatz rikatz mentioned this issue Sep 15, 2021
Closed
3 tasks
@rikatz
Copy link
Contributor Author

rikatz commented Sep 21, 2021

/close

Image downgraded and will be available next release

@k8s-ci-robot
Copy link
Contributor

@rikatz: Closing this issue.

In response to this:

/close

Image downgraded and will be available next release

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
v1.0.1
Development

Successfully merging a pull request may close this issue.

Downgrade nginx to v1.19 and apply openresty patches rikatz/ingress-nginx
2 participants
@rikatz @k8s-ci-robot