Goal Summary:
There is currently no way to tell if v4 is active, either on central itself or any secure clusters. Since v4 needs to be enabled on all the secured clusters, we need to know which ones are actually running v4 or not. To this point we had enabled v4 and thought it was working, only to find out later that the secured clusters are not running v4 as they should. I would also request that the documentation regarding the switch to v4 be updated as there is almost nothing describing the full process.
Goals and expected user outcomes:
A way to get the status of ScannerV4 for both Central and Secured Cluster
Acceptance Criteria:
A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.
<enter general Feature acceptance here>
Success Criteria or KPIs measured:
A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.
<enter success criteria and/or KPIs here>
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.
<your text here>
Out of Scope (Optional):
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
- is related to
-
RFE-7269 [UX] - An easy way to identify Scanner v4 vs v2 for both Central and Secured Cluster
-
- Approved
-