apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "39726"
    uid: 447454ef-7df8-4b41-8319-d545a454d991
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:54:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 872.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 900.039µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:06:31Z"
    - latency: 916.345µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:05:31Z"
    - latency: 730.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:04:31Z"
    - latency: 984.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:03:31Z"
    - latency: 1.025548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:02:31Z"
    - latency: 960.422µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:01:31Z"
    - latency: 796.681µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:31Z"
    - latency: 840.899µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "42854"
    uid: a2d7802c-b87e-4c36-945d-784cef066f5e
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:53:31Z"
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.583581ms
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 8.229075ms
      message: 'load-balancer-api-external: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 5.199604ms
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 9.145514ms
      message: 'load-balancer-api-external: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 5.296723ms
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 8.306808ms
      message: 'load-balancer-api-external: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 5.018898ms
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 8.497312ms
      message: 'load-balancer-api-external: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 5.791527ms
      message: 'load-balancer-api-external: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 8.02415ms
      message: 'load-balancer-api-external: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:07:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "42853"
    uid: 97bc592f-537f-4b35-8ae0-0e512987ee59
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:53:31Z"
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.571586ms
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 8.153266ms
      message: 'load-balancer-api-internal: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 4.580295ms
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 9.121377ms
      message: 'load-balancer-api-internal: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 5.065248ms
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 8.270483ms
      message: 'load-balancer-api-internal: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 4.212157ms
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 8.447251ms
      message: 'load-balancer-api-internal: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 3.9726ms
      message: 'load-balancer-api-internal: tcp connection to a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 8.000656ms
      message: 'load-balancer-api-internal: resolved host name a9780e54bdea94e00a8c7204cd178772-020c1969e9085718.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:07:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-network-check-target-ip-10-0-134-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "39725"
    uid: bd9cc4f8-3410-4a55-a327-75a5361ef1ee
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:54:31Z"
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.499343ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 2.215397ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 2.761974ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:06:31Z"
    - latency: 2.380287ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:05:31Z"
    - latency: 2.428955ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:04:31Z"
    - latency: 2.262649ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:03:31Z"
    - latency: 2.160347ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:02:31Z"
    - latency: 2.158943ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:01:31Z"
    - latency: 1.976991ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:31Z"
    - latency: 2.313835ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "39723"
    uid: 292ece81-8e2e-46a8-bed4-960b571d4996
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:54:31Z"
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 749.591µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 707.612µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 1.159101ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:06:31Z"
    - latency: 871.595µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:05:31Z"
    - latency: 992.965µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:04:31Z"
    - latency: 848.014µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:03:31Z"
    - latency: 1.202612ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:02:31Z"
    - latency: 1.010868ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:01:31Z"
    - latency: 871.962µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:31Z"
    - latency: 724.562µs
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-network-check-target-ip-10-0-141-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "39724"
    uid: 40ad48b0-e9cb-4ff6-b2f7-296a7d4f512b
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:54:31Z"
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.496449ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 1.867833ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 1.625936ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:06:31Z"
    - latency: 1.857012ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:05:31Z"
    - latency: 1.843443ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:04:31Z"
    - latency: 2.091081ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:03:31Z"
    - latency: 1.813213ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:02:31Z"
    - latency: 2.150009ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:01:31Z"
    - latency: 1.641145ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:31Z"
    - latency: 1.606999ms
      message: 'network-check-target-ip-10-0-141-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:47:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-153-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-153.ec2.internal
      uid: 2d6f6cb7-2c14-4c35-a417-6e27588f2a0b
    resourceVersion: "42852"
    uid: 69c2860b-09be-462a-a17e-eb92c0d750de
  spec:
    sourcePod: network-check-source-dbd9cf844-bf74n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:53:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 1.779423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:31Z"
    - latency: 1.144337ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 1.658111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:31Z"
    - latency: 887.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 1.61017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:09:31Z"
    - latency: 759.499µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 1.814213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:08:31Z"
    - latency: 836.774µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:31Z"
    - latency: 2.084014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:07:31Z"
kind: List
metadata:
  resourceVersion: ""