apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48206"
    uid: d7ec52b0-9bc5-4861-8042-7ab93257b054
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:01:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.705µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 1.119533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 1.040237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 994.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 1.452526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:01Z"
    - latency: 1.407669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:01Z"
    - latency: 1.046974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:01Z"
    - latency: 1.191886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:01Z"
    - latency: 974.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:01Z"
    - latency: 956.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48987"
    uid: 19aed7fa-c19e-4857-878d-38e8e47cd22d
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:00:01Z"
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.568805ms
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 6.474305ms
      message: 'load-balancer-api-external: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 5.000757ms
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 8.237856ms
      message: 'load-balancer-api-external: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 5.382431ms
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 7.380185ms
      message: 'load-balancer-api-external: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 6.208215ms
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 7.323733ms
      message: 'load-balancer-api-external: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 4.035259ms
      message: 'load-balancer-api-external: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 7.492872ms
      message: 'load-balancer-api-external: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48988"
    uid: b5833993-53a8-4963-bb50-60e62a87e6b3
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:00:01Z"
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.633497ms
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 6.337618ms
      message: 'load-balancer-api-internal: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 5.177701ms
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 8.185709ms
      message: 'load-balancer-api-internal: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 5.322592ms
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 7.61789ms
      message: 'load-balancer-api-internal: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 6.37555ms
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 7.269944ms
      message: 'load-balancer-api-internal: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 4.155337ms
      message: 'load-balancer-api-internal: tcp connection to a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 7.364855ms
      message: 'load-balancer-api-internal: resolved host name a6db7a207d6b64e36a873df556a38fb3-1416a23d8811a43b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-network-check-target-ip-10-0-131-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48205"
    uid: 3d27eb67-fcb7-42ea-8936-289d1ed514d9
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:01:01Z"
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066754ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 2.253275ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 2.474363ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 3.061786ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 2.225662ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:01Z"
    - latency: 2.33514ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:01Z"
    - latency: 2.854237ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:01Z"
    - latency: 1.996356ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:01Z"
    - latency: 2.343006ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:01Z"
    - latency: 2.193814ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-network-check-target-ip-10-0-140-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48203"
    uid: 41c2a643-31cb-4756-a715-64f9240cf7a2
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:01:01Z"
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.077661ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 2.251188ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 2.349848ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 2.980175ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 2.186821ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:01Z"
    - latency: 2.425718ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:01Z"
    - latency: 2.301868ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:01Z"
    - latency: 2.040703ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:01Z"
    - latency: 2.473839ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:01Z"
    - latency: 2.142566ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-network-check-target-ip-10-0-142-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48204"
    uid: 2bcb25f5-3a63-4190-98ea-3c73f42a3631
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:01:01Z"
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.263766ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 980.727µs
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 1.50348ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 791.502µs
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 943.554µs
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:01Z"
    - latency: 1.488024ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:01Z"
    - latency: 1.095971ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:01Z"
    - latency: 926.077µs
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:01Z"
    - latency: 1.151897ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:01Z"
    - latency: 918.552µs
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-134.ec2.internal
      uid: 16c55661-0e9e-4d91-be07-7cd075eac01e
    resourceVersion: "48985"
    uid: 598117d0-f994-47ca-b0c7-3ad0b9e4bf52
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rww
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:00:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 1.649904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:01Z"
    - latency: 829.172µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 1.737348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:01Z"
    - latency: 1.037209ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 2.338201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:28:01Z"
    - latency: 964.417µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 1.708932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:01Z"
    - latency: 1.923308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:01Z"
    - latency: 1.739065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:01Z"
kind: List
metadata:
  resourceVersion: ""