apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "55534"
    uid: 05f03e65-6196-4945-8276-9144a0182fbb
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:36:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.177388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 1.097423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 1.184932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 1.024929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 1.417321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:00:03Z"
    - latency: 1.604884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:59:03Z"
    - latency: 1.049168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:58:03Z"
    - latency: 909.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:57:03Z"
    - latency: 1.161279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:56:03Z"
    - latency: 1.427198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:55:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "56498"
    uid: 976e5de6-dab3-41a6-8f41-8904e32fa7f1
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:35:03Z"
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.790637ms
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 7.114353ms
      message: 'load-balancer-api-external: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 4.108461ms
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 7.182443ms
      message: 'load-balancer-api-external: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 3.85565ms
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 6.916717ms
      message: 'load-balancer-api-external: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 4.270488ms
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 6.375257ms
      message: 'load-balancer-api-external: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 4.149488ms
      message: 'load-balancer-api-external: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 6.938652ms
      message: 'load-balancer-api-external: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "56499"
    uid: ed3ced11-5220-4d3c-b50e-bb31806208d3
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:35:03Z"
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.957439ms
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 7.152273ms
      message: 'load-balancer-api-internal: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 4.096478ms
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 7.272269ms
      message: 'load-balancer-api-internal: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 3.218151ms
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 6.997318ms
      message: 'load-balancer-api-internal: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 4.312202ms
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 6.431313ms
      message: 'load-balancer-api-internal: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 4.878987ms
      message: 'load-balancer-api-internal: tcp connection to a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 6.995656ms
      message: 'load-balancer-api-internal: resolved host name a0b6d83eabbd44768a21dc68c0c2d6b1-8edacd391d4c15ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-network-check-target-ip-10-0-130-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "55532"
    uid: 77c59195-8cf4-4c16-a664-c2f83b504bc7
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:36:03Z"
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.541101ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 2.338705ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 2.52035ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 2.264682ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 2.769435ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:00:03Z"
    - latency: 2.502303ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:59:03Z"
    - latency: 2.542015ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:58:03Z"
    - latency: 2.410366ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:57:03Z"
    - latency: 2.729795ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:56:03Z"
    - latency: 2.554256ms
      message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:55:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-network-check-target-ip-10-0-136-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "55531"
    uid: ceff6113-935f-4efa-a584-156f24d77b61
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:36:03Z"
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026707ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 1.326014ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 1.023642ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 1.1738ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 1.710479ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:00:03Z"
    - latency: 859.966µs
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:59:03Z"
    - latency: 982.862µs
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:58:03Z"
    - latency: 946.467µs
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:57:03Z"
    - latency: 1.357761ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:56:03Z"
    - latency: 1.465175ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:55:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-network-check-target-ip-10-0-142-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "55533"
    uid: 67379237-a974-455f-ace4-8af963a3c7ee
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:36:03Z"
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.247264ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 2.314478ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 2.200645ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 2.030597ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 2.721882ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:00:03Z"
    - latency: 2.221542ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:59:03Z"
    - latency: 2.374124ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:58:03Z"
    - latency: 2.302238ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:57:03Z"
    - latency: 2.184558ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:56:03Z"
    - latency: 2.790241ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:55:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T16:29:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-76-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-76.ec2.internal
      uid: f4d9279c-0248-4dc1-8638-fd2404e388a2
    resourceVersion: "56497"
    uid: 12158975-2545-42d1-beb6-51344eac6231
  spec:
    sourcePod: network-check-source-869dcfcdcd-hq4sc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T16:35:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.314µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 1.778056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:05:03Z"
    - latency: 756.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 1.874976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:04:03Z"
    - latency: 1.279763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 1.691776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:03:03Z"
    - latency: 837.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 1.710898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:02:03Z"
    - latency: 904.216µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T17:01:03Z"
    - latency: 1.693743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T17:01:03Z"
kind: List
metadata:
  resourceVersion: ""