apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "39332"
    uid: b830fe17-2c28-422f-8897-4d00246cf2b6
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.453µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:12:19Z"
    - latency: 1.283556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 1.016891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 1.022593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 1.18503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 1.067452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 1.065162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:06:19Z"
    - latency: 1.010863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:19Z"
    - latency: 968.089µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:19Z"
    - latency: 960.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "38706"
    uid: 4c472425-de10-4941-8650-c81b2bf91eb9
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:19Z"
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.8168ms
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 8.131767ms
      message: 'load-balancer-api-external: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 4.089059ms
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 8.210399ms
      message: 'load-balancer-api-external: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 6.082063ms
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 8.803349ms
      message: 'load-balancer-api-external: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 3.545795ms
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 10.08787ms
      message: 'load-balancer-api-external: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 5.65914ms
      message: 'load-balancer-api-external: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 8.449949ms
      message: 'load-balancer-api-external: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:07:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "38705"
    uid: 97d41116-0dda-4bd7-9d04-f22aa573cfcd
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:19Z"
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.828987ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 8.062143ms
      message: 'load-balancer-api-internal: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 5.532306ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 8.315906ms
      message: 'load-balancer-api-internal: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 6.03686ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 8.842241ms
      message: 'load-balancer-api-internal: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 4.443614ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 10.178159ms
      message: 'load-balancer-api-internal: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 4.646056ms
      message: 'load-balancer-api-internal: tcp connection to ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 8.492732ms
      message: 'load-balancer-api-internal: resolved host name ab0ff79c81e0f4d80aef34d9b68c4fea-40281bcd2c84228c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:07:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-network-check-target-ip-10-0-130-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "39330"
    uid: 7b65880e-0798-4889-ab62-8e6c982045d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:19Z"
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.532697ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:12:19Z"
    - latency: 2.215638ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 2.385944ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 2.385811ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 2.503532ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 2.651206ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 2.28222ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:06:19Z"
    - latency: 2.273233ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:19Z"
    - latency: 2.109692ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:19Z"
    - latency: 2.127592ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-network-check-target-ip-10-0-141-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "39329"
    uid: 99f906b1-2534-42ba-a12c-7f55c4ceadfc
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:19Z"
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 765.673µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:12:19Z"
    - latency: 919.833µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 920.246µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 936.335µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 1.23907ms
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 897.035µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 768.277µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:06:19Z"
    - latency: 940.988µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:19Z"
    - latency: 1.19909ms
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:19Z"
    - latency: 907.57µs
      message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-network-check-target-ip-10-0-143-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "39331"
    uid: e126b071-702a-4708-b7ef-3159c2b6855f
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:19Z"
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.53666ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:12:19Z"
    - latency: 2.731595ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 2.51725ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 2.355774ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 2.474039ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 2.214779ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 2.286848ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:06:19Z"
    - latency: 2.471343ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:05:19Z"
    - latency: 2.362629ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:04:19Z"
    - latency: 1.980928ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-100.ec2.internal
      uid: 4bd70dcb-88e5-47e7-b1aa-9fa415036886
    resourceVersion: "38704"
    uid: 461e11ad-f73a-4921-8515-594a3953e1aa
  spec:
    sourcePod: network-check-source-7cbc45fddc-nk6nh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 1.675212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:11:19Z"
    - latency: 739.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 1.945249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:10:19Z"
    - latency: 779.205µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 1.8961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:09:19Z"
    - latency: 772.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 1.756485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:08:19Z"
    - latency: 851.992µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:07:19Z"
    - latency: 1.840737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:07:19Z"
kind: List
metadata:
  resourceVersion: ""