Skip to content

OSDOCS-19632: Document propagation of Annotations and Labels from Rules to ComplianceCheckResults#111334

Open
GroceryBoyJr wants to merge 3 commits intoopenshift:mainfrom
GroceryBoyJr:OSDOCS-19632
Open

OSDOCS-19632: Document propagation of Annotations and Labels from Rules to ComplianceCheckResults#111334
GroceryBoyJr wants to merge 3 commits intoopenshift:mainfrom
GroceryBoyJr:OSDOCS-19632

Conversation

@GroceryBoyJr
Copy link
Copy Markdown
Contributor

@GroceryBoyJr GroceryBoyJr commented May 6, 2026

GroceryBoyJr and others added 3 commits May 6, 2026 17:19
Add assembly and modules describing propagation of custom labels and
annotations from Rule and CustomRule objects to ComplianceCheckResult
resources, based on the compliance-operator enhancement and CMP-3974.

Register the new topic under Compliance Operator scan management.

Co-authored-by: Cursor <cursoragent@cursor.com>
Clarify that operator versions are not aligned with OCP and link to the
Compliance Operator lifecycle section on the support page.

Co-authored-by: Cursor <cursoragent@cursor.com>
Operator release cadence is covered in OpenShift release notes; keep only
the 1.9.0 prerequisite here.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 6, 2026

@GroceryBoyJr: This pull request references OSDOCS-19632 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):

Issue: https://redhat.atlassian.net/browse/OSDOCS-19632

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 6, 2026
@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 6, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown


:_mod-docs-content-type: PROCEDURE
[id="compliance-operator-checkresult-custom-metadata-configure-customrules_{context}"]
= Adding custom labels and annotations to a CustomRule object for CEL scans
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.


:_mod-docs-content-type: PROCEDURE
[id="compliance-operator-checkresult-custom-metadata-configure-rules_{context}"]
= Adding custom labels and annotations to a Rule object
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.


:_mod-docs-content-type: CONCEPT
[id="compliance-operator-checkresult-custom-metadata-overview_{context}"]
= Understanding custom metadata on rules and check results
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.


Failure behavior:: If the operator cannot build its in-memory index of `Rule` objects during aggregation, it logs a warning and still creates scan results without your custom metadata. If a label value violates Kubernetes length or syntax rules, creation of that specific `ComplianceCheckResult` can fail while other results continue.

For more background on the enhancement, see link:https://github.com/ComplianceAsCode/compliance-operator/blob/master/enhancements/custom-metadata-propagation.md[Custom metadata propagation from rules to ComplianceCheckResults] and link:https://redhat.atlassian.net/browse/CMP-3974[CMP-3974].
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.


Failure behavior:: If the operator cannot build its in-memory index of `Rule` objects during aggregation, it logs a warning and still creates scan results without your custom metadata. If a label value violates Kubernetes length or syntax rules, creation of that specific `ComplianceCheckResult` can fail while other results continue.

For more background on the enhancement, see link:https://github.com/ComplianceAsCode/compliance-operator/blob/master/enhancements/custom-metadata-propagation.md[Custom metadata propagation from rules to ComplianceCheckResults] and link:https://redhat.atlassian.net/browse/CMP-3974[CMP-3974].
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.

@@ -0,0 +1,23 @@
:_mod-docs-content-type: ASSEMBLY
[id="compliance-operator-checkresult-custom-metadata"]
= Propagating custom metadata to ComplianceCheckResult objects
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

@GroceryBoyJr: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants