This message contains interactive elements.

Set that time to a good estimate of how long you feel it takes to “exrcise” your apps through any testing. If it flips to Monitor and you start getting alerts for behavior you feel is innocuous, just add that rule via the alerts; no need to roll a group back to monitor to wait for that behavior again.

Be sure to understand the details of how this works https://open-docs.neuvector.com/policy/modes#automated-promotion-of-group-modes

..

B. Consider exporting CRDs when an app stack has finished the dev/test cycle and perhaps the Qa cycle you are already performing. Even if you didn’t automate this via the API, manually exporting CRDs via the UI burns very very little time; just let Neuvector follow along with the app lifecycle phases you are already using.