CNV#50738: Doc: Update downstream doc Delete Protection for VMs by aspauldi · Pull Request #90981 · openshift/openshift-docs

aspauldi · 2025-03-24T15:49:39Z

Version(s): 4.19+

Links to docs preview:

QE review:

QE has approved this change.

Additional information: This PR covers both the CLI (CNV-50738) and the web console (CNV-49592) implementations of the VM delete protection feature. SMEs Javier Cano Cano and Phillip Rhodes and QE engineers Leon Kladnitsky and Geetika Kapoor have all approved this PR.

ocpdocs-previewbot · 2025-03-24T15:59:07Z

🤖 Tue Apr 22 15:28:52 - Prow CI generated the docs preview:

https://90981--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/managing_vms/virt-delete-vms.html
https://90981--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/managing_vms/virt-enabling-disabling-vm-delete-protection.html
https://90981--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/virt/managing_vms/virt-delete-vms.html
https://90981--ocpdocs-pr.netlify.app/openshift-rosa/latest/virt/managing_vms/virt-delete-vms.html

openshift-ci-robot · 2025-03-25T16:11:56Z

@aspauldi: This pull request references HPUX-549 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 "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.19+

Issue: CNV-50738

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 · 2025-03-25T16:14:58Z

@aspauldi: This pull request references CNV-45952 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 sub-task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.19+

Issue: CNV-50738

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 · 2025-03-25T16:15:08Z

@aspauldi: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Version(s): 4.19+

Issue: CNV-50738

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.

jcanocan

As general comment, I would state that the VM delete protection is off by default or is an opt-in feature.

Also, I think we should include a section of opt-out VM delete protection entirely. In other words, how can cluster admins can prevent cluster users to enable this feature in their deployments.

ocpdocs-vale-bot · 2025-04-02T16:40:38Z

+// * virt/managing-vms/virt-enabling-disabling-vm-delete-protection.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-removing-vm-delete-protection{context}"]


🤖 [error] OpenShiftAsciiDoc.IdHasContextVariable: ID is missing the '_{context}' variable at the end of the ID.

ocpdocs-vale-bot · 2025-04-02T16:40:39Z

+
+= Removing the virtual machine delete protection option
+
+When you enable delete protection on a VM (virtual machine), you ensure that the VM cannot be inadvertently deleted.  You can also choose to disable the protection for a VM.


🤖 [error] RedHat.Spacing: Keep one space between words in 'deleted. You'. For more information, see RedHat.Spacing.

ocpdocs-vale-bot · 2025-04-02T16:40:40Z

+
+.Example configuration file
+[source,yaml]
+----


🤖 [error] AsciiDoc.ValidCodeBlocks: Unterminated listing block found in file.

When I lint this YAML file, I get the following error:

Missing closing "quote at line 17, column 170
Implicit keys need to be on a single line at line 18, column 5

Looks like it could use a check-over.

Checking again with Javier. The YAML file had an issue earlier, and Javier provide a new file. Not sure what the issue is now.

Let's try like this now:

apiVersion: admissionregistration.k8s.io/v1 kind: ValidatingAdmissionPolicy metadata: name: "disable-vm-delete-protection" spec: failurePolicy: Fail matchConstraints: resourceRules: - apiGroups: ["kubevirt.io"] apiVersions: ["*"] operations: ["UPDATE", "CREATE"] resources: ["virtualmachines"] variables: - expression: string('kubevirt.io/vm-delete-protection') name: vmDeleteProtectionLabel validations: - expression: >- !has(object.metadata.labels) || !object.metadata.labels.exists(label, label == variables.vmDeleteProtectionLabel) || has(oldObject.metadata.labels) && oldObject.metadata.labels.exists(label, label == variables.vmDeleteProtectionLabel) message: "Virtual Machine delete protection feature is disabled"

ocpdocs-vale-bot · 2025-04-02T16:40:41Z

+----
+
+
+apiVersion: admissionregistration.k8s.io/v1


🤖 [error] RedHat.TermsErrors: Use 'Kubernetes' rather than 'k8s'. For more information, see RedHat.TermsErrors.

CNV docs use k8s all over the place, so no change made here.

Hmm, @aireilly is that a new bug in CI? I've never seen this pop up as an error in the apiVersion field before.

Fixed this in https://github.com/redhat-documentation/vale-at-red-hat/pull/933/files

jcanocan

This is looking great! Just a couple of suggestions.

jcanocan · 2025-04-03T07:59:15Z

+
+= Enabling or disabling virtual machine delete protection by using the command line
+
+To prevent the inadvertent deletion of a virtual machine, you can enable virtual machine delete protection by using the command line. The feature is disabled by default.


Suggested change

To prevent the inadvertent deletion of a virtual machine, you can enable virtual machine delete protection by using the command line. The feature is disabled by default.

To prevent the inadvertent deletion of a virtual machine, you can enable virtual machine delete protection by using the command line. Virtual machines are not delete protected by default.

Feel free to ignore this suggestion. But I feel that this may lead to think that you need to enable the feature cluster-wide and then enable the protection for each vm.

jcanocan · 2025-04-03T07:59:57Z

+
+= Enabling or disabling virtual machine delete protection by using the web console
+
+To prevent the inadvertent deletion of a virtual machine, you can enable virtual machine delete protection by using the {product-title} web console. The feature is disabled by default.


Same as above.

jcanocan · 2025-04-04T14:39:57Z

Thanks for all effort @aspauldi!
IHMO, it looks awesome! 😊

bergerhoffer · 2025-04-15T19:09:09Z

/label peer-review-in-progress

bergerhoffer

A few bits of feedback, let me know if you have any questions!

bergerhoffer · 2025-04-15T19:40:47Z

+
+When you enable delete protection on a VM (virtual machine), you ensure that the VM cannot be inadvertently deleted. You can also choose to disable the protection for a VM.
+
+As a cluster administrator, you can choose not to make the VM delete protection option available. VMs with delete protection already enabled retain that setting; for any new VMs that are created, enabling the option is not allowed.


"choose not to make" sounds a little wordy. Maybe something like this?

Also a suggestion for the second sentence.

Suggested change

As a cluster administrator, you can choose not to make the VM delete protection option available. VMs with delete protection already enabled retain that setting; for any new VMs that are created, enabling the option is not allowed.

As a cluster administrator, you can remove the VM delete protection option completely. VMs with delete protection already enabled retain that setting; any new VMs that are created do not have delete protection as an option.

@aspauldi Looks like this comment was missed.

bergerhoffer · 2025-04-15T19:47:14Z

+  validationActions: [Deny]
+  matchResources:
+----
+


This procedure only creates the YAML files - it doesn't actually apply them to the cluster. I'd recommend adding two more steps for applying them.

Here's an example of another procedure that does this: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/security_and_compliance/index#installing-nbde-tang-server-operator-using-cli_installing-nbde-tang-server-operator

@jcanocan and @geetikakay, the documentation peer reviewer Andrea Hoffer recommended adding two steps to this procedure. Can you please take a look and see if what I have added is correct? Thanks! The procedure is documented here: https://90981--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/managing_vms/virt-enabling-disabling-vm-delete-protection#virt-removing-vm-delete-protection_virt-enabling-disabling-vm-delete-protection

@aspauldi Sure, I will review again. But I have a quick question:
When enabling vm-delete-protection, we patch the VM with a label like this:

-- enable labels
$ oc patch vm <vm_name> --type merge -p '{"metadata":{"labels":{"kubevirt.io/vm-delete-protection":"True"}}}' -n

To disable it, there can be two approaches:

Set the label value to "False"

$ oc patch vm <vm_name> --type merge -p '{"metadata":{"labels":{"kubevirt.io/vm-delete-protection":"False"}}}' -n

Remove the label entirely
$ oc patch vm <vm_name> --type json -p '[{"op": "remove", "path": "/metadata/labels/kubevirt.io~1vm-delete-protection"}]' -n

Should we treat disabling (setting to "False") and removing the label as two different cases? Technically, both result in the same outcomethe protection is no longer enforced. But from a documentation or behavior clarity perspective, does it make sense to distinguish between them?

cc @jcanocan

Hi @geetikakay, I think that we can keep the procedure just to one method to make it easier for the users. Thanks!

@bergerhoffer's suggestion sounds fine to me! Great idea.
@geetikakay's suggestion makes sense. However, I have chosen the approach of removing the label to keep the final yaml manifest as sort as possible. I tend to agree with @aspauldi. Thanks for the suggestion, nevertheless.

Looks like this was done, as I see an oc apply here. Is this resolved?

Yes, the steps were added.

bergerhoffer · 2025-04-15T19:49:14Z

/label peer-review-done
/remove-label peer-review-needed
/remove-label peer-review-in-progress

aspauldi · 2025-04-21T15:38:28Z

@geetikakay, can you confirm that you approve this PR? Thanks.

ShaunaDiaz

Couple of pre-merge Qs, @aspauldi. Thank you!

ShaunaDiaz · 2025-04-21T17:55:27Z

+
+When you enable delete protection on a VM (virtual machine), you ensure that the VM cannot be inadvertently deleted. You can also choose to disable the protection for a VM.
+
+As a cluster administrator, you can choose not to make the VM delete protection option available. VMs with delete protection already enabled retain that setting; for any new VMs that are created, enabling the option is not allowed.


@aspauldi Looks like this comment was missed.

ShaunaDiaz · 2025-04-21T17:57:16Z

+
+.Example configuration file
+[source,yaml]
+----


When I lint this YAML file, I get the following error:

Missing closing "quote at line 17, column 170
Implicit keys need to be on a single line at line 18, column 5

Looks like it could use a check-over.

ShaunaDiaz · 2025-04-21T17:58:25Z

+  validationActions: [Deny]
+  matchResources:
+----
+


Looks like this was done, as I see an oc apply here. Is this resolved?

geetikakay · 2025-04-22T13:23:02Z

lgtm

aspauldi · 2025-04-22T14:42:23Z

@ShaunaDiaz, can you take another look? I believe all the merge review comments have been resolved. Thanks!

ShaunaDiaz

a few nits; still one unresolved comment from peer review

ShaunaDiaz · 2025-04-22T14:42:24Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-enabling-disabling-vm-delete-protection-cli_{context}"]
+


Suggested change

delete extra line

ShaunaDiaz · 2025-04-22T14:43:21Z

+:_mod-docs-content-type: PROCEDURE
+[id="virt-enabling-disabling-vm-delete-protection-cli_{context}"]
+
+= Enabling or disabling virtual machine delete protection by using the command line


Suggested change

= Enabling or disabling virtual machine delete protection by using the command line

= Enabling or disabling VM delete protection by using the command line

I think you can get away with VM in the headline since you define it right away in text. Be more scannable for users.

ShaunaDiaz · 2025-04-22T14:43:57Z

+
+= Enabling or disabling virtual machine delete protection by using the command line
+
+To prevent the inadvertent deletion of a virtual machine (VM), you can enable virtual machine delete protection by using the command line. You can also disable delete protection for a VM.


Suggested change

To prevent the inadvertent deletion of a virtual machine (VM), you can enable virtual machine delete protection by using the command line. You can also disable delete protection for a VM.

To prevent the inadvertent deletion of a virtual machine (VM), you can enable VM delete protection by using the command line. You can also disable delete protection for a VM.

ShaunaDiaz · 2025-04-22T14:45:03Z

+// * virt/managing-vms/virt-enabling-disabling-vm-delete-protection.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-enabling-disabling-vm-delete-protection-cli_{context}"]


IMHO these should be two separate one-command procedures, not a single one. Probably want to modularize these some time later prior to DITA migration.

I can do that in another PR; thanks.

ShaunaDiaz · 2025-04-22T14:45:56Z

+
+.Prerequisites
+
+* You have installed the {oc-first}.


You also need to know the VMs you want to protect or allow to be deleted, right?

Andrea had me remove that prereq in her peer review.

ShaunaDiaz · 2025-04-22T14:46:14Z

+:_mod-docs-content-type: PROCEDURE
+[id="virt-enabling-disabling-vm-delete-protection-web_{context}"]
+
+= Enabling or disabling virtual machine delete protection by using the web console


Suggested change

= Enabling or disabling virtual machine delete protection by using the web console

= Enabling or disabling VM delete protection by using the web console

ShaunaDiaz · 2025-04-22T14:46:25Z

+
+= Enabling or disabling virtual machine delete protection by using the web console
+
+To prevent the inadvertent deletion of a virtual machine (VM), you can enable virtual machine delete protection by using the {product-title} web console. You can also disable delete protection for a VM.


Suggested change

To prevent the inadvertent deletion of a virtual machine (VM), you can enable virtual machine delete protection by using the {product-title} web console. You can also disable delete protection for a VM.

To prevent the inadvertent deletion of a virtual machine (VM), you can enable VM delete protection by using the {product-title} web console. You can also disable delete protection for a VM.

ShaunaDiaz · 2025-04-22T14:47:41Z

+:_mod-docs-content-type: PROCEDURE
+[id="virt-removing-vm-delete-protection_{context}"]
+
+= Removing the virtual machine delete protection option


Suggested change

= Removing the virtual machine delete protection option

= Removing the VM delete protection option

ShaunaDiaz · 2025-04-22T14:47:50Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-removing-vm-delete-protection_{context}"]
+


Suggested change

openshift-ci · 2025-04-22T15:30:08Z

@aspauldi: 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.

aspauldi · 2025-04-22T15:30:38Z

/label merge-review-needed

jab-rh · 2025-04-23T01:51:32Z

/cherry-pick enterprise-4.19

openshift-cherrypick-robot · 2025-04-23T01:52:20Z

@jab-rh: new pull request created: #92505

Details

In response to this:

/cherry-pick enterprise-4.19

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.

openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 24, 2025

aspauldi closed this Mar 24, 2025

aspauldi reopened this Mar 24, 2025

openshift-ci Bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 24, 2025

ocpdocs-vale-bot reviewed Mar 24, 2025

View reviewed changes

Comment thread modules/virt-enabling-vm-delete-protection-web.adoc Outdated

aspauldi closed this Mar 25, 2025

aspauldi reopened this Mar 25, 2025

aspauldi changed the title ~~CNV#50738: Doc: Update downstream doc Delete Protection for VMs~~ CNV#50738 and HPUX-549: Doc: Update downstream doc Delete Protection for VMs Mar 25, 2025

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 25, 2025

aspauldi changed the title ~~CNV#50738 and HPUX-549: Doc: Update downstream doc Delete Protection for VMs~~ CNV#50738 and CNV-45952: Doc: Update downstream doc Delete Protection for VMs Mar 25, 2025

aspauldi changed the title ~~CNV#50738 and CNV-45952: Doc: Update downstream doc Delete Protection for VMs~~ CNV#50738 and CNV#45952: Doc: Update downstream doc Delete Protection for VMs Mar 25, 2025

openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 25, 2025

aspauldi changed the title ~~CNV#50738 and CNV#45952: Doc: Update downstream doc Delete Protection for VMs~~ CNV#50738 and CNV#49592: Doc: Update downstream doc Delete Protection for VMs Mar 25, 2025

jcanocan reviewed Mar 26, 2025

View reviewed changes

Comment thread modules/virt-enabling-disabling-vm-delete-protection-web.adoc Outdated

jcanocan reviewed Mar 26, 2025

View reviewed changes

Comment thread virt/managing_vms/virt-enabling-disabling-vm-delete-protection.adoc Outdated

aspauldi changed the title ~~CNV#50738 and CNV#49592: Doc: Update downstream doc Delete Protection for VMs~~ CNV#50738: Doc: Update downstream doc Delete Protection for VMs Mar 26, 2025

aspauldi force-pushed the CNV-50738 branch from 8261779 to 68384f8 Compare April 1, 2025 16:43

openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 2, 2025

ocpdocs-vale-bot reviewed Apr 2, 2025

View reviewed changes

jcanocan reviewed Apr 3, 2025

View reviewed changes

aspauldi force-pushed the CNV-50738 branch from 37d809b to 48b6b62 Compare April 15, 2025 19:03

openshift-ci Bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Apr 15, 2025

bergerhoffer reviewed Apr 15, 2025

View reviewed changes

openshift-ci Bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Apr 15, 2025

aspauldi force-pushed the CNV-50738 branch 2 times, most recently from 1860b47 to 27fce7c Compare April 21, 2025 15:13

openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 21, 2025

ShaunaDiaz removed the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 21, 2025

ShaunaDiaz reviewed Apr 21, 2025

View reviewed changes

aspauldi force-pushed the CNV-50738 branch from fe0c769 to 16ca469 Compare April 22, 2025 13:29

ShaunaDiaz reviewed Apr 22, 2025

View reviewed changes

openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 22, 2025

fix merge conflicts

7e75a9d

aspauldi force-pushed the CNV-50738 branch from b29e4b4 to 7e75a9d Compare April 22, 2025 15:20

jab-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 23, 2025

jab-rh merged commit 81bb74b into openshift:main Apr 23, 2025
2 checks passed

openshift-cherrypick-robot mentioned this pull request Apr 23, 2025

[enterprise-4.19] CNV#50738: Doc: Update downstream doc Delete Protection for VMs #92505

Merged

jab-rh removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label May 29, 2025


		= Removing the virtual machine delete protection option

		When you enable delete protection on a VM (virtual machine), you ensure that the VM cannot be inadvertently deleted. You can also choose to disable the protection for a VM.


		= Enabling or disabling virtual machine delete protection by using the command line

		To prevent the inadvertent deletion of a virtual machine, you can enable virtual machine delete protection by using the command line. The feature is disabled by default.


		When you enable delete protection on a VM (virtual machine), you ensure that the VM cannot be inadvertently deleted. You can also choose to disable the protection for a VM.

		As a cluster administrator, you can choose not to make the VM delete protection option available. VMs with delete protection already enabled retain that setting; for any new VMs that are created, enabling the option is not allowed.

	As a cluster administrator, you can choose not to make the VM delete protection option available. VMs with delete protection already enabled retain that setting; for any new VMs that are created, enabling the option is not allowed.
	As a cluster administrator, you can remove the VM delete protection option completely. VMs with delete protection already enabled retain that setting; any new VMs that are created do not have delete protection as an option.


		:_mod-docs-content-type: PROCEDURE
		[id="virt-enabling-disabling-vm-delete-protection-cli_{context}"]

	= Enabling or disabling virtual machine delete protection by using the command line
	= Enabling or disabling VM delete protection by using the command line

	= Removing the virtual machine delete protection option
	= Removing the VM delete protection option


		:_mod-docs-content-type: PROCEDURE
		[id="virt-removing-vm-delete-protection_{context}"]

Conversation

aspauldi commented Mar 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Mar 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 25, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 25, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 25, 2025

Uh oh!

jcanocan left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jcanocan left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jcanocan commented Apr 4, 2025

Uh oh!

bergerhoffer commented Apr 15, 2025

Uh oh!

bergerhoffer left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aspauldi Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

geetikakay Apr 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

aspauldi commented Mar 24, 2025 •

edited

Loading

ocpdocs-previewbot commented Mar 24, 2025 •

edited

Loading

openshift-ci-robot commented Mar 25, 2025 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Mar 25, 2025 •

edited by openshift-ci Bot

Loading

aspauldi Apr 16, 2025 •

edited

Loading

geetikakay Apr 17, 2025 •

edited

Loading