apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "21708"
    uid: b8d1f92a-bf21-4fbb-aa5a-4b09be9468e0
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:57:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.019µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:36Z"
    - latency: 790.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:36Z"
    - latency: 1.154725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:36Z"
    - latency: 1.562866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 1.413146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 1.39293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 980.094µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 1.168988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 1.103698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:36Z"
    - latency: 1.193301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "20369"
    uid: 594e4964-0205-494c-ad63-df8d27120972
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:56:36Z"
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.150016ms
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 9.883032ms
      message: 'load-balancer-api-external: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 4.799992ms
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 10.334807ms
      message: 'load-balancer-api-external: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 4.975066ms
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 11.195614ms
      message: 'load-balancer-api-external: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 5.537235ms
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 14.815539ms
      message: 'load-balancer-api-external: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 6.187186ms
      message: 'load-balancer-api-external: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 12.637279ms
      message: 'load-balancer-api-external: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "20370"
    uid: 41283581-ee45-47bf-af23-07455f61288c
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:56:36Z"
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.003211ms
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 9.925161ms
      message: 'load-balancer-api-internal: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 4.761445ms
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 10.3549ms
      message: 'load-balancer-api-internal: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 4.972609ms
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 11.234356ms
      message: 'load-balancer-api-internal: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 5.528621ms
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 14.860782ms
      message: 'load-balancer-api-internal: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 6.190938ms
      message: 'load-balancer-api-internal: tcp connection to ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 12.7231ms
      message: 'load-balancer-api-internal: resolved host name ac6f23c8024e143d4968b4e9ddc32fe9-b200e2ac2d964347.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-network-check-target-ip-10-0-133-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "21706"
    uid: c3407570-3e32-4f8a-a723-e325529bcdf9
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:57:36Z"
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.29939ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:36Z"
    - latency: 2.354016ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:36Z"
    - latency: 2.377428ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:36Z"
    - latency: 2.378104ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 2.092368ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 2.13888ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 2.038486ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 2.241504ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 2.093579ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:36Z"
    - latency: 2.286931ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-network-check-target-ip-10-0-136-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "21705"
    uid: ba5ac41e-cf62-4058-aa9f-ab5842bebfb9
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:57:36Z"
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051619ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:36Z"
    - latency: 1.465163ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:36Z"
    - latency: 1.356937ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:36Z"
    - latency: 1.093309ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 941.104µs
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 1.581192ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 991.282µs
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 1.543345ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 862.684µs
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:36Z"
    - latency: 1.04958ms
      message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-network-check-target-ip-10-0-137-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "21707"
    uid: d27a6fa7-68bc-4005-8280-e669d0b26e22
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:57:36Z"
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305724ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:36Z"
    - latency: 2.340052ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:36Z"
    - latency: 2.688514ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:36Z"
    - latency: 2.452313ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 1.964741ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 2.193546ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 2.325831ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 2.484309ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 2.157749ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:36Z"
    - latency: 3.19087ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:50:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-90.ec2.internal
      uid: 3eb47d82-c12f-40c3-8cdb-eb5c6dbe8d86
    resourceVersion: "20368"
    uid: a3cb9306-84ad-451c-9f8e-ef5135b59005
  spec:
    sourcePod: network-check-source-56499946bc-6ddkj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:56:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.248µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 2.360704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:08:36Z"
    - latency: 911.331µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 2.387645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:07:36Z"
    - latency: 1.015012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 1.836032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:36Z"
    - latency: 917.065µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 1.87543ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:36Z"
    - latency: 1.205358ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:36Z"
    - latency: 2.084583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:36Z"
kind: List
metadata:
  resourceVersion: ""