Skip to content

Update violations page info #91288

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

Merged
merged 1 commit into from
Apr 3, 2025
Merged

Update violations page info #91288

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 14 additions & 10 deletions modules/analyzing-all-violations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,18 +11,22 @@ By viewing the *Violations* page, you can analyze all violations and take correc
.Procedure

. In the {product-title-short} portal, click *Violations*.
. To navigate through the different types of violations, do any of the following tasks:
** To view the list of active violations, click the *Active* tab.
** To view the list of resolved violations, click the *Resolved* tab.
** To view the list of violations that {product-title-short} attempted to resolve, click the *Attempted* tab.
. Choose the appropriate method to view the violations from the drop-down list, which is in the upper left of the page:
** To display the findings for application workloads, select *Applications view*.
** To display the findings for platform components in {ocp}, select *Platform view*.
** To display the findings for application workloads and platform components simultaneously, select *Full view*.
. Optional: Choose the appropriate method to re-organize the information in the *Violations* page:
. Click one of the following tabs to view violations by category:
** *User Workloads*: Displays violations for user-managed workloads.
** *Platform*: Displays violations for workloads used by {ocp} and layered services.
** *All violations*: Displays violations for user workloads and platform components. It also displays audit log violations for cluster resources.
. Click one of the following tabs to view violations by type:
** *Active*: Displays violations in the build and deploy stages or unresolved runtime violations.
** *Resolved*: Displays the following violations:
*** Violations in the build and deploy stages for workloads that were removed or modified to be compliant
*** Manually resolved runtime violations
*** Violations that were generated before a policy exclusion was added
** *Attempted*: Displays violations for deployment actions that were attempted but blocked by the evaluation of enforced policies. For example, if the admission controller detected that the attempted deployment action, such as a deployment create, update, or scale, would cause a policy violation, it prevented the operation from running in the cluster.
. Optional: Choose a method to reorganize or filter information on the *Violations* page:
** To sort the violations in ascending or descending order, select a column heading.
** To filter violations, use the filter bar.
** To see more details about the violation, select a violation in the *Violations* page.
. Optional: Choose the appropriate method to exclude a deployment from the policy:
** If you selected a single deployment, click the overflow menu {kebab} and then select *Exclude deployment from policy*.
** If you selected multiple deployments, from the *Row actions* drop-down list, select *Exclude deployments from policy*.
** If you selected multiple deployments, from the *Row actions* drop-down list, select *Exclude deployments from policy*.
//Do we need to add an explanation for "Mark as resolved"?