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

Validate NGINX Ingress Controller with the latest version of NGINX AppProtect #7086

Open
shaun-nx opened this issue Jan 8, 2025 · 1 comment
Labels
proposal An issue that proposes a feature request
Milestone

Comments

@shaun-nx
Copy link
Contributor

shaun-nx commented Jan 8, 2025

Overview

The latest version of NGINX AppProtect will bring with it the ability for multiple bundles compiled with different attack signature to be processed. In our case, this means:

  1. Being able to deploy more than one VirtualServer with a waf policy attached, where each policy references a bundle that is a compiled with a different attack signature.
  2. Being able to deploy more than one Ingress resource that references a compile policy, where each bundle is a compiled with a different attack signature.

Use case

This capability, provided by version X of NGINX AppProtect, ensure that Ingress and VirtualServer resources can continue to use policies that are compiled with older versions of attack signatures, while also allowing other Ingress and VirtualServer resources to update their compiled bundles with the latest attack signatures.

@shaun-nx shaun-nx added the proposal An issue that proposes a feature request label Jan 8, 2025
@shaun-nx shaun-nx added this to the v4.1.0 milestone Jan 8, 2025
Copy link

github-actions bot commented Jan 8, 2025

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
Projects
Status: Todo ☑
Development

No branches or pull requests

1 participant