MON-4383: feat(auto_docs_examples): adjust and add more examples #2573

machine424 · 2025-02-28T15:30:07Z

I added CHANGELOG entry for this change.
No user facing changes, so no entry in CHANGELOG was needed.

openshift-ci · 2025-02-28T15:30:41Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [machine424]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-bot · 2025-07-03T01:00:33Z

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot · 2025-08-02T08:30:10Z

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot · 2025-09-02T00:01:17Z

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci · 2025-09-02T00:01:51Z

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

machine424 · 2025-09-02T07:04:17Z

/reopen

openshift-ci · 2025-09-02T07:04:31Z

@machine424: Reopened this PR.

In response to this:

/reopen

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.

machine424 · 2025-09-22T08:35:33Z

test/e2e/test_command/scripts/openshift-monitoring_alertmanager-main_service_port_9092.yaml

+        --serviceaccount=test-alertmanager-tenancy-monitoring-rules-edit:am-client
+      TOKEN=$(oc create token am-client --namespace=test-alertmanager-tenancy-monitoring-rules-edit)
+      CA_CERT=$(oc get secret router-certs-default -n openshift-ingress -o jsonpath='{.data.tls\.crt}' | base64 --decode)
+      curl --cacert <(printf "%s" "$CA_CERT") --fail -H "Authorization: Bearer $TOKEN" "https://alertmanager-main.openshift-monitoring:9092/api/v2/alerts?namespace=test-alertmanager-tenancy-monitoring-rules-edit"


machine424 · 2025-10-01T13:28:40Z

jsonnet/utils/add-annotations.libsonnet

      s + '.'
    else if namespace != '' then
-      s + ' in the `%s` project.'
+      s + ' in the `%s` project.' % namespace


this is needed for the PR

machine424 · 2025-10-02T07:00:41Z

/retitle MON-4383: feat(auto_docs_examples): adjust and add more examples

openshift-ci-robot · 2025-10-02T07:00:49Z

@machine424: This pull request references MON-4383 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

I added CHANGELOG entry for this change.

No user facing changes, so no entry in CHANGELOG was needed.

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.

machine424 · 2025-10-02T07:00:50Z

/retest-required

machine424 · 2025-10-02T07:02:29Z

/skip

eromanova97

Hello @machine424 I have added a few suggestions for the wording and format. Thanks!

eromanova97 · 2025-10-02T08:30:05Z

Documentation/resources.adoc

+$ curl -k -H "Authorization: Bearer $TOKEN" "https://$ROUTE/api/v2/alerts?filter=alertname=Watchdog"
+# The endpoints can also be accessed from within the cluster.
+$ curl -k -H "Authorization: Bearer $TOKEN" "https://alertmanager-main.openshift-monitoring:9094/api/v2/alerts?filter=alertname=Watchdog"
+----


A few small suggestions for better flow:

Suggested change

----

+

The following example exercises permissions granted by the `monitoring-alertmanager-view` role. The binding commands must be run by a user with the necessary privileges.

+

[source,terminal]

----

# Create a test namespace and a service account.

$ oc create namespace test-alertmanager-web-monitoring-alertmanager-view

$ oc create serviceaccount am-client --namespace=test-alertmanager-web-monitoring-alertmanager-view

# Bind the role to the service account.

# The binding in this example is applied to a service account but can also be applied to any user.

$ oc create rolebinding test-alertmanager-web-monitoring-alertmanager-view \

--namespace=openshift-monitoring \

--role=monitoring-alertmanager-view \

--serviceaccount=test-alertmanager-web-monitoring-alertmanager-view:am-client

# Generate a token to access the endpoints.

$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-view)

# Access Alertmanager endpoints externally.

$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})

$ curl -k -H "Authorization: Bearer $TOKEN" "https://$ROUTE/api/v2/alerts?filter=alertname=Watchdog"

# Access Alertmanager endpoints from within the cluster.

$ curl -k -H "Authorization: Bearer $TOKEN" "https://alertmanager-main.openshift-monitoring:9094/api/v2/alerts?filter=alertname=Watchdog"

----

eromanova97 · 2025-10-02T08:31:36Z

Documentation/resources.adoc

+----
+# The following example exercises permissions granted by the monitoring-alertmanager-edit Role.
+# The binding commands are supposed to run by a user with the necessary privileges.
+$ oc create namespace test-alertmanager-web-monitoring-alertmanager-edit


Suggested change

----

# The following example exercises permissions granted by the monitoring-alertmanager-edit Role.

# The binding commands are supposed to run by a user with the necessary privileges.

$ oc create namespace test-alertmanager-web-monitoring-alertmanager-edit

+

The following example exercises permissions granted by the `monitoring-alertmanager-edit` role. The binding commands must be run by a user with the necessary privileges.

+

[source,terminal]

----

# Create a test namespace and a service account.

$ oc create namespace test-alertmanager-web-monitoring-alertmanager-edit

eromanova97 · 2025-10-02T08:32:24Z

Documentation/resources.adoc

+$ oc create serviceaccount am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit
+# The binding is done to a ServiceAccount, but it can also be applied to any other user.
+$ oc create rolebinding test-alertmanager-web-monitoring-alertmanager-edit \
+  --namespace=openshift-monitoring \
+  --role=monitoring-alertmanager-edit \
+  --serviceaccount=test-alertmanager-web-monitoring-alertmanager-edit:am-client


Suggested change

$ oc create serviceaccount am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit

# The binding is done to a ServiceAccount, but it can also be applied to any other user.

$ oc create rolebinding test-alertmanager-web-monitoring-alertmanager-edit \

--namespace=openshift-monitoring \

--role=monitoring-alertmanager-edit \

--serviceaccount=test-alertmanager-web-monitoring-alertmanager-edit:am-client

$ oc create serviceaccount am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit

# Bind the role to the service account.

# The binding in this example is applied to a service account but can also be applied to any user.

$ oc create rolebinding test-alertmanager-web-monitoring-alertmanager-edit \

--namespace=openshift-monitoring \

--role=monitoring-alertmanager-edit \

--serviceaccount=test-alertmanager-web-monitoring-alertmanager-edit:am-client

eromanova97 · 2025-10-02T08:34:07Z

Documentation/resources.adoc

+# The token can then be used to access the endpoints on the port.
+$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit)


Suggested change

# The token can then be used to access the endpoints on the port.

$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit)

# Generate a token to access the endpoints on the port.

$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit)

eromanova97 · 2025-10-02T08:36:04Z

Documentation/resources.adoc

+$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})
+$ curl -k -X POST  "https://$ROUTE/api/v2/silences" \


Suggested change

$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})

$ curl -k -X POST "https://$ROUTE/api/v2/silences" \

# Access Alertmanager endpoints externally.

$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})

$ curl -k -X POST "https://$ROUTE/api/v2/silences" \

eromanova97 · 2025-10-02T08:59:52Z

Documentation/resources.adoc

+----
+----
+# The following example exercises permissions granted by the monitoring-edit Cluster Role.
+# The binding commands are supposed to run by a user with the necessary privileges.
+$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-edit


Suggested change

----

----

# The following example exercises permissions granted by the monitoring-edit Cluster Role.

# The binding commands are supposed to run by a user with the necessary privileges.

$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-edit

----

+

The following example exercises permissions granted by the `monitoring-edit` cluster role. The binding commands must be run by a user with the necessary privileges.

+

[source,terminal]

----

# Create a test namespace and a service account.

$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-edit

eromanova97 · 2025-10-02T09:00:02Z

Documentation/resources.adoc

+# The binding commands are supposed to run by a user with the necessary privileges.
+$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-edit
+$ oc create serviceaccount thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-edit
+# The binding is done to a Service Account, but it can also be applied to any other user.


Suggested change

# The binding is done to a Service Account, but it can also be applied to any other user.

# Bind the role to the service account.

# The binding in this example is applied to a service account but can also be applied to any user.

eromanova97 · 2025-10-02T09:00:15Z

Documentation/resources.adoc

+  --namespace=test-thanos-querier-tenancy-rules-monitoring-edit \
+  --clusterrole=monitoring-edit \
+  --serviceaccount=test-thanos-querier-tenancy-rules-monitoring-edit:thanos-client
+# The token can then be used to access the endpoints.


Suggested change

# The token can then be used to access the endpoints.

# Generate a token to access the endpoints.

eromanova97 · 2025-10-02T09:00:27Z

Documentation/resources.adoc

+  --serviceaccount=test-thanos-querier-tenancy-rules-monitoring-edit:thanos-client
+# The token can then be used to access the endpoints.
+$ TOKEN=$(oc create token thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-edit)
+# Because the port is not exposed by default, the endpoint is assumed to be accessed from within the cluster.


Suggested change

# Because the port is not exposed by default, the endpoint is assumed to be accessed from within the cluster.

# Access Alertmanager endpoints from within the cluster. The port is not exposed externally by default.

eromanova97 · 2025-10-02T09:01:31Z

Documentation/resources.adoc

+----
+----
+# The following example exercises permissions granted by the monitoring-rules-view Cluster Role.
+# The binding commands are supposed to run by a user with the necessary privileges.
+$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-rules-view
+$ oc create serviceaccount thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view
+# The binding is done to a Service Account, but it can also be applied to any other user.
+$ oc create rolebinding test-thanos-querier-tenancy-rules-monitoring-rules-view \
+  --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view \
+  --clusterrole=monitoring-rules-view \
+  --serviceaccount=test-thanos-querier-tenancy-rules-monitoring-rules-view:thanos-client
+# The token can then be used to access the endpoints.
+$ TOKEN=$(oc create token thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view)
+# Because the port is not exposed by default, the endpoint is assumed to be accessed from within the cluster.
+$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/rules?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"
+$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/alerts?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"
+----


Suggested change

----

----

# The following example exercises permissions granted by the monitoring-rules-view Cluster Role.

# The binding commands are supposed to run by a user with the necessary privileges.

$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-rules-view

$ oc create serviceaccount thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view

# The binding is done to a Service Account, but it can also be applied to any other user.

$ oc create rolebinding test-thanos-querier-tenancy-rules-monitoring-rules-view \

--namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view \

--clusterrole=monitoring-rules-view \

--serviceaccount=test-thanos-querier-tenancy-rules-monitoring-rules-view:thanos-client

# The token can then be used to access the endpoints.

$ TOKEN=$(oc create token thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view)

# Because the port is not exposed by default, the endpoint is assumed to be accessed from within the cluster.

$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/rules?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"

$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/alerts?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"

----

----

+

The following example exercises permissions granted by the `monitoring-rules-view` cluster role. The binding commands must be run by a user with the necessary privileges.

+

[source,terminal]

----

# Create a test namespace and a service account.

$ oc create namespace test-thanos-querier-tenancy-rules-monitoring-rules-view

$ oc create serviceaccount thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view

# Bind the role to the service account.

# The binding in this example is applied to a service account but can also be applied to any user.

$ oc create rolebinding test-thanos-querier-tenancy-rules-monitoring-rules-view \

--namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view \

--clusterrole=monitoring-rules-view \

--serviceaccount=test-thanos-querier-tenancy-rules-monitoring-rules-view:thanos-client

# Generate a token to access the endpoints.

$ TOKEN=$(oc create token thanos-client --namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view)

# Access Alertmanager endpoints from within the cluster. The port is not exposed externally by default.

$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/rules?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"

$ curl -k -f -H "Authorization: Bearer $TOKEN" "https://thanos-querier.openshift-monitoring:9093/api/v1/alerts?namespace=test-thanos-querier-tenancy-rules-monitoring-rules-view"

----

eromanova97

Hello @machine424 I have added a few suggestions for the wording and format. Thanks!

openshift-ci · 2025-10-02T13:26:59Z

@machine424: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-single-node	`9852ee0`	link	false	`/test e2e-aws-ovn-single-node`
ci/prow/e2e-hypershift-conformance	`9852ee0`	link	true	`/test e2e-hypershift-conformance`
ci/prow/e2e-agnostic-operator	`9852ee0`	link	true	`/test e2e-agnostic-operator`
ci/prow/e2e-aws-ovn-upgrade	`9852ee0`	link	true	`/test e2e-aws-ovn-upgrade`
ci/prow/ginkgo-tests	`9852ee0`	link	false	`/test ginkgo-tests`
ci/prow/e2e-aws-ovn-techpreview	`9852ee0`	link	true	`/test e2e-aws-ovn-techpreview`
ci/prow/okd-scos-e2e-aws-ovn	`9852ee0`	link	false	`/test okd-scos-e2e-aws-ovn`

Full PR test history. Your PR dashboard.

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.

openshift-ci bot requested review from danielmellado and rexagod February 28, 2025 15:30

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 28, 2025

machine424 force-pushed the doc2 branch from af9a75a to 9829e2a Compare February 28, 2025 18:39

machine424 mentioned this pull request Apr 3, 2025

OCPBUGS-54211: return rules from tenancy endpoint #2585

Closed

2 tasks

openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 3, 2025

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 3, 2025

openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 2, 2025

openshift-ci bot closed this Sep 2, 2025

openshift-ci bot reopened this Sep 2, 2025

machine424 force-pushed the doc2 branch from 774e1c9 to 07f514f Compare September 22, 2025 08:33

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 22, 2025

machine424 commented Sep 22, 2025

View reviewed changes

machine424 force-pushed the doc2 branch 2 times, most recently from 8b95877 to 93e521a Compare October 1, 2025 13:27

machine424 commented Oct 1, 2025

View reviewed changes

machine424 force-pushed the doc2 branch 3 times, most recently from 338bdea to 7475bb0 Compare October 1, 2025 20:11

openshift-ci bot changed the title ~~feat(auto_docs_examples): adjust and add more examples~~ MON-4383: feat(auto_docs_examples): adjust and add more examples Oct 2, 2025

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

eromanova97 reviewed Oct 2, 2025

View reviewed changes

machine424 added 3 commits October 2, 2025 12:27

feat(auto_docs_examples): adjust and add more examples

ab6cb5e

feat(auto_docs_examples): add examples to Documentation/resources.adoc

921bc35

chore: adjust

9852ee0

machine424 force-pushed the doc2 branch from 417a1d7 to 9852ee0 Compare October 2, 2025 10:27

-----
++
+The following example exercises permissions granted by the `monitoring-alertmanager-view` role. The binding commands must be run by a user with the necessary privileges.
++
+[source,terminal]
+----
+# Create a test namespace and a service account.
+$ oc create namespace test-alertmanager-web-monitoring-alertmanager-view
+$ oc create serviceaccount am-client --namespace=test-alertmanager-web-monitoring-alertmanager-view
+# Bind the role to the service account.
+# The binding in this example is applied to a service account but can also be applied to any user.
+$ oc create rolebinding test-alertmanager-web-monitoring-alertmanager-view \
+  --namespace=openshift-monitoring \
+  --role=monitoring-alertmanager-view \
+  --serviceaccount=test-alertmanager-web-monitoring-alertmanager-view:am-client
+# Generate a token to access the endpoints.
+$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-view)
+# Access Alertmanager endpoints externally.
+$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})
+$ curl -k -H "Authorization: Bearer $TOKEN" "https://$ROUTE/api/v2/alerts?filter=alertname=Watchdog"
+# Access Alertmanager endpoints from within the cluster.
+$ curl -k -H "Authorization: Bearer $TOKEN" "https://alertmanager-main.openshift-monitoring:9094/api/v2/alerts?filter=alertname=Watchdog"
+----

		# The token can then be used to access the endpoints on the port.
		$ TOKEN=$(oc create token am-client --namespace=test-alertmanager-web-monitoring-alertmanager-edit)

		$ ROUTE=$(oc get route alertmanager-main --namespace=openshift-monitoring -ojsonpath={.spec.host})
		$ curl -k -X POST "https://$ROUTE/api/v2/silences" \

	# The binding is done to a Service Account, but it can also be applied to any other user.
	# Bind the role to the service account.
	# The binding in this example is applied to a service account but can also be applied to any user.

	# The token can then be used to access the endpoints.
	# Generate a token to access the endpoints.

	# Because the port is not exposed by default, the endpoint is assumed to be accessed from within the cluster.
	# Access Alertmanager endpoints from within the cluster. The port is not exposed externally by default.

MON-4383: feat(auto_docs_examples): adjust and add more examples #2573

Are you sure you want to change the base?

MON-4383: feat(auto_docs_examples): adjust and add more examples #2573

Uh oh!

Conversation

machine424 commented Feb 28, 2025

Uh oh!

openshift-ci bot commented Feb 28, 2025

Uh oh!

openshift-bot commented Jul 3, 2025

Uh oh!

openshift-bot commented Aug 2, 2025

Uh oh!

openshift-bot commented Sep 2, 2025

Uh oh!

openshift-ci bot commented Sep 2, 2025

Uh oh!

machine424 commented Sep 2, 2025

Uh oh!

openshift-ci bot commented Sep 2, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

machine424 commented Oct 2, 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 Oct 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

machine424 commented Oct 2, 2025

Uh oh!

machine424 commented Oct 2, 2025

Uh oh!

eromanova97 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!

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!

eromanova97 left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Oct 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

machine424 commented Oct 2, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Oct 2, 2025 •

edited by openshift-ci bot

Loading