You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/user-guide-v1beta2.adoc
+4-10Lines changed: 4 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -443,15 +443,11 @@ Once a `RuntimeComponent` application is exposed as a Provisioned Service, a ser
443
443
444
444
=== Monitoring
445
445
446
-
Runtime Component Operator can create a `ServiceMonitor` resource to integrate with `Prometheus Operator`.
446
+
Runtime Component Operator can create a Prometheus `ServiceMonitor` resource to integrate with `Prometheus Operator` once installed.
447
447
448
-
Monitoring can be leveraged by users on Red Hat OpenShift Container Platform. Before using the feature, you must install `Prometheus Operator` by following our link:++https://github.com/OpenLiberty/open-liberty-operator/blob/main/doc/openshift-monitoring.adoc++[Application Monitoring] guide.
448
+
Monitoring can be leveraged by users on Red Hat OpenShift Container Platform v4.6+. Before using the feature, you must install `Prometheus Operator` by following our link:++https://github.com/OpenLiberty/open-liberty-operator/blob/main/doc/openshift-monitoring.adoc#application-monitoring-on-rhocp-46++[Application Monitoring on RHOCP 4.6+] guide. Configure the `RuntimeComponent` CR instance with the basic or advanced monitoring specification below, then view Prometheus Metrics through the OpenShift UI as "Administrator" under the `Observe` > `Metrics` tab.
449
449
450
-
_The community edition of Prometheus Operator is not supported for users on Red Hat OpenShift Container Platform._
451
-
452
-
_This feature does not support integration with Knative Service._
453
-
454
-
_Prometheus Operator is required to use ServiceMonitor._
450
+
_This feature does not support community versions of Prometheus Operator and integration with Knative Service._
455
451
456
452
==== Basic monitoring specification
457
453
@@ -472,7 +468,7 @@ spec:
472
468
473
469
==== Advanced monitoring specification
474
470
475
-
For advanced scenarios, it is possible to set many `ServiceMonitor` settings such as authentication secret using link:++https://github.com/coreos/prometheus-operator/blob/main/Documentation/api.md#endpoint++[Prometheus Endpoint]
471
+
For advanced scenarios, it is possible to set many `ServiceMonitor` settings such as authentication secret using link:++https://github.com/coreos/prometheus-operator/blob/main/Documentation/api.md#endpoint++[Prometheus Endpoint]. Ensure that the `basicAuth` secrets (i.e. `metrics-secret`) are created and visible to Runtime Component Operator.
476
472
477
473
[source,yaml]
478
474
----
@@ -498,8 +494,6 @@ spec:
498
494
insecureSkipVerify: true
499
495
----
500
496
501
-
Runtime Component Operator will not create/update the `ServiceMonitor` if the `basicAuth` secrets are not defined.
502
-
503
497
=== Knative support
504
498
505
499
Runtime Component Operator can deploy serverless applications with link:++https://knative.dev/docs/++[Knative] on a Kubernetes cluster. To achieve this, the operator creates a link:++https://github.com/knative/serving/blob/main/docs/spec/spec.md#service++[Knative `Service`] resource which manages the whole life cycle of a workload.
0 commit comments