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
You can configure the `linuxptp` services (`ptp4l`, `phc2sys`) as boundary clocks for dual NIC hardware by creating a `PtpConfig` custom resource (CR) object for each NIC.
10
13
11
14
Dual NIC hardware allows you to connect each NIC to the same upstream leader clock with separate `ptp4l` instances for each NIC feeding the downstream clocks.
You can configure `linuxptp` services and use PTP-capable hardware in {product-title} cluster nodes.
11
10
12
11
[id="about-using-ptp-hardware"]
13
12
== About PTP hardware
14
13
15
-
You can configure `linuxptp` services and use PTP-capable hardware in {product-title} cluster nodes.
16
-
17
-
[NOTE]
18
-
====
19
-
The PTP Operator works with PTP-capable devices on clusters provisioned only on bare-metal infrastructure.
20
-
====
21
-
22
14
You can use the {product-title} console or OpenShift CLI (`oc`) to install PTP by deploying the PTP Operator. The PTP Operator creates and manages the `linuxptp` services and provides the following features:
23
15
24
16
* Discovery of the PTP-capable devices in the cluster.
@@ -27,6 +19,11 @@ You can use the {product-title} console or OpenShift CLI (`oc`) to install PTP b
27
19
28
20
* Notification of PTP clock events that negatively affect the performance and reliability of your application with the PTP Operator `cloud-event-proxy` sidecar.
29
21
22
+
[NOTE]
23
+
====
24
+
The PTP Operator works with PTP-capable devices on clusters provisioned only on bare-metal infrastructure.
0 commit comments