apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "79048"
    uid: 5824d635-aa4b-49ac-a2ba-af7bd73d403e
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:36:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 925.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 950.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:28Z"
    - latency: 1.15293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:28Z"
    - latency: 1.38289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:28Z"
    - latency: 1.094973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:28Z"
    - latency: 1.168046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:28Z"
    - latency: 822.895µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:28Z"
    - latency: 1.114514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:28Z"
    - latency: 982.003µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "85268"
    uid: 16cbbd91-a0ab-4626-913b-dfe01a53d674
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:35:28Z"
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.120648ms
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 7.721067ms
      message: 'load-balancer-api-external: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 4.828326ms
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 7.644734ms
      message: 'load-balancer-api-external: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 4.210742ms
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 6.634479ms
      message: 'load-balancer-api-external: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 5.71229ms
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 8.031804ms
      message: 'load-balancer-api-external: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 5.793925ms
      message: 'load-balancer-api-external: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 7.770241ms
      message: 'load-balancer-api-external: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:31:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "85267"
    uid: 935dbee7-ef18-4e94-b960-dc85a0c3356a
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:35:28Z"
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.164043ms
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 7.650832ms
      message: 'load-balancer-api-internal: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 4.808377ms
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 7.707198ms
      message: 'load-balancer-api-internal: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 4.212457ms
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 6.50112ms
      message: 'load-balancer-api-internal: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 5.002843ms
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 7.982635ms
      message: 'load-balancer-api-internal: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 5.786361ms
      message: 'load-balancer-api-internal: tcp connection to a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 7.75124ms
      message: 'load-balancer-api-internal: resolved host name a5f95260c63ad49e6beeb76df3c29ca2-915245ed3e4141b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:31:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-130-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "79045"
    uid: 8680f11b-6df2-4c70-ad3f-68d95b16f583
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:36:28Z"
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.951µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 1.575388ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 833.776µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:28Z"
    - latency: 897.211µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:28Z"
    - latency: 1.085068ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:28Z"
    - latency: 886.072µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:28Z"
    - latency: 1.318769ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:28Z"
    - latency: 1.082402ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:28Z"
    - latency: 1.38636ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:28Z"
    - latency: 933.855µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-134-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "79046"
    uid: d8bc23fd-54d8-41c7-9e5d-db3f6a32e94e
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:36:28Z"
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.444905ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 1.705689ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 1.847612ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:28Z"
    - latency: 2.112888ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:28Z"
    - latency: 2.369616ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:28Z"
    - latency: 2.004792ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:28Z"
    - latency: 2.095561ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:28Z"
    - latency: 2.090835ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:28Z"
    - latency: 2.171919ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:28Z"
    - latency: 2.124381ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-143-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "79047"
    uid: 1348086a-930c-462d-8cdd-88a00257047a
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:36:28Z"
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.20657ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 1.866946ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 2.271568ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:28Z"
    - latency: 1.962094ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:28Z"
    - latency: 2.22025ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:28Z"
    - latency: 2.226956ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:28Z"
    - latency: 2.110443ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:28Z"
    - latency: 2.131435ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:28Z"
    - latency: 2.061036ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:28Z"
    - latency: 2.363898ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:29:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: ac3e146e-553b-4805-8a2b-fe1740a38070
    resourceVersion: "85266"
    uid: cc2d0687-9700-4de7-a16a-71fa3c4ad31d
  spec:
    sourcePod: network-check-source-7d88cb55d8-nmd8v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:35:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 1.721098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:35:28Z"
    - latency: 1.253316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 1.735016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:34:28Z"
    - latency: 1.005699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 1.652644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:33:28Z"
    - latency: 838.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 1.888709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:32:28Z"
    - latency: 752.711µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:28Z"
    - latency: 2.110897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:31:28Z"
kind: List
metadata:
  resourceVersion: ""