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.

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

Upgrade guide for NGINX Ingress Controller + AppProtect WAF v4 to AppProtect WAF v5 #6853

Open
shaun-nx opened this issue Nov 22, 2024 · 1 comment
Labels
proposal An issue that proposes a feature request ready for refinement An issue that was triaged and it is ready to be refined
Milestone

Comments

@shaun-nx
Copy link
Contributor

Overview

Overview

As a user of NGINX Ingress Controller, configured with NAP v4, I would like to have clear documentation on how to move from NAP v4 to NAP v5 so that I can ensure the move from v4 to v5 is as smooth as possible

High-level Requirements

  • Ensure documentation covers all dependencies required to be in place before moving from v4 to v5
  • Ensure compatibility between different WAF component version are known and documented
  • Ensure existing compatibility with Ingress resource is documented
  • Ensure existing compatibility with VirtualServer resource is documented
  • Ensure that, if any component is required to be present before NIC is deploy, that this is clearly documented
@shaun-nx shaun-nx added proposal An issue that proposes a feature request ready for refinement An issue that was triaged and it is ready to be refined labels Nov 22, 2024
@shaun-nx shaun-nx added this to the v4.1.0 milestone Nov 22, 2024
Copy link

Hi @shaun-nx thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal An issue that proposes a feature request ready for refinement An issue that was triaged and it is ready to be refined
Projects
Status: Todo ☑
Development

No branches or pull requests

1 participant