apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "46839"
    uid: b6f8b2be-188f-4df9-a871-f46f45afd2e5
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:38:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 1.223018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 1.169718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 907.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:56:54Z"
    - latency: 1.177098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:55:54Z"
    - latency: 1.241122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:54:54Z"
    - latency: 1.149845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:53:54Z"
    - latency: 871.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:52:54Z"
    - latency: 977.257µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:51:54Z"
    - latency: 1.227641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "48988"
    uid: a7aa2f72-7563-49f2-915c-3791c86647e4
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:37:54Z"
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.03031ms
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 10.223586ms
      message: 'load-balancer-api-external: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 5.642623ms
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 6.855881ms
      message: 'load-balancer-api-external: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 4.988885ms
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 7.715763ms
      message: 'load-balancer-api-external: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 4.254931ms
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 8.135941ms
      message: 'load-balancer-api-external: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 3.535408ms
      message: 'load-balancer-api-external: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 9.326559ms
      message: 'load-balancer-api-external: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:57:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "48987"
    uid: 68d69969-da9d-4135-a90d-5ace499b5e47
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:37:54Z"
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.028588ms
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 10.342594ms
      message: 'load-balancer-api-internal: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 5.659928ms
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 6.830869ms
      message: 'load-balancer-api-internal: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 5.674656ms
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 7.648444ms
      message: 'load-balancer-api-internal: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 4.252003ms
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 8.204344ms
      message: 'load-balancer-api-internal: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 4.03263ms
      message: 'load-balancer-api-internal: tcp connection to a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 9.433169ms
      message: 'load-balancer-api-internal: resolved host name a85419e366bf2473eb384feae4512072-41e1434c7af5cd42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:57:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-129-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "46836"
    uid: f205699d-604b-418c-a810-f599b3ce1d52
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:38:54Z"
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250291ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 2.344924ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 2.536541ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 2.912902ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:56:54Z"
    - latency: 2.597741ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:55:54Z"
    - latency: 2.186596ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:54:54Z"
    - latency: 2.149842ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:53:54Z"
    - latency: 2.292802ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:52:54Z"
    - latency: 2.234125ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:51:54Z"
    - latency: 2.341494ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-129-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "46835"
    uid: fcd89c6a-cb29-4bea-983b-1d44ed9e3e2d
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:38:54Z"
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.122µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 1.155349ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 879.41µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 926.219µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:56:54Z"
    - latency: 944.724µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:55:54Z"
    - latency: 1.474086ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:54:54Z"
    - latency: 857.922µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:53:54Z"
    - latency: 1.127449ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:52:54Z"
    - latency: 1.181728ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:51:54Z"
    - latency: 1.147571ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-138-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "46837"
    uid: 16c07162-c0ea-408c-9ae0-00b842ba6da8
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:38:54Z"
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.361012ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 2.282125ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 2.347024ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 2.582146ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:56:54Z"
    - latency: 2.605945ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:55:54Z"
    - latency: 2.646546ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:54:54Z"
    - latency: 2.44681ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:53:54Z"
    - latency: 2.120563ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:52:54Z"
    - latency: 2.152994ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:51:54Z"
    - latency: 2.315432ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T23:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 69d57aee-3510-499e-b1d7-a31757f42dc3
    resourceVersion: "48984"
    uid: 0c647754-2383-48b3-a5de-db6cd420e61d
  spec:
    sourcePod: network-check-source-dbd9cf844-cv54b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:37:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004002ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 2.092454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:01:54Z"
    - latency: 1.181296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 1.940631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-04T00:00:54Z"
    - latency: 802.733µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 2.13542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:59:54Z"
    - latency: 766.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 1.749222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:58:54Z"
    - latency: 1.12909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:57:54Z"
    - latency: 1.836663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:57:54Z"
kind: List
metadata:
  resourceVersion: ""