apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "120539"
    uid: 988a7331-7d7f-4c73-8bf4-fb9514593483
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:35:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.474241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 1.271131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 973.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 963.169µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:51Z"
    - latency: 997.901µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:51Z"
    - latency: 923.323µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:51Z"
    - latency: 1.134803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:51Z"
    - latency: 1.27665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:51Z"
    - latency: 888.142µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:51Z"
    - latency: 2.116625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "123561"
    uid: 2ea272ce-7eb4-457a-bc34-62aab3b02930
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:34:51Z"
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.702258ms
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 7.22541ms
      message: 'load-balancer-api-external: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 60.764864ms
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 7.707824ms
      message: 'load-balancer-api-external: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 52.024232ms
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 7.997145ms
      message: 'load-balancer-api-external: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 54.871173ms
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 6.990339ms
      message: 'load-balancer-api-external: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 51.563168ms
      message: 'load-balancer-api-external: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 9.638997ms
      message: 'load-balancer-api-external: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "123562"
    uid: 7faa1dfc-95a2-4c02-91d9-40793b8321ce
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:34:51Z"
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.776824ms
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 7.186802ms
      message: 'load-balancer-api-internal: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 51.87647ms
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 7.800664ms
      message: 'load-balancer-api-internal: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 51.98013ms
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 8.053601ms
      message: 'load-balancer-api-internal: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 51.473617ms
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 6.90439ms
      message: 'load-balancer-api-internal: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 51.718036ms
      message: 'load-balancer-api-internal: tcp connection to a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 9.654622ms
      message: 'load-balancer-api-internal: resolved host name a0c1794a904604bf0bf421b952c83549-4b7c0d71fd7f1dce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-130-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "120536"
    uid: 2567f5eb-407e-41ca-9f9a-034e945f33e7
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:35:51Z"
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.98453ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 2.986544ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 3.498464ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 2.434726ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:51Z"
    - latency: 2.605696ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:51Z"
    - latency: 2.745891ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:51Z"
    - latency: 2.898721ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:51Z"
    - latency: 2.931126ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:51Z"
    - latency: 2.864424ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:51Z"
    - latency: 3.305414ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-131-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "120535"
    uid: 4e642125-8298-4234-b921-adb43b39e96e
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:35:51Z"
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.966627ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 2.64433ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 2.757006ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 2.628061ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:51Z"
    - latency: 2.500251ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:51Z"
    - latency: 2.77063ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:51Z"
    - latency: 2.714566ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:51Z"
    - latency: 2.852206ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:51Z"
    - latency: 1.932333ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:51Z"
    - latency: 2.995601ms
      message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-134-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "120534"
    uid: c07aa139-4d33-4aaf-8598-999ac806cdd5
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:35:51Z"
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990854ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 1.36648ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 808.729µs
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 1.016435ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:51Z"
    - latency: 878.153µs
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:51Z"
    - latency: 2.378745ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:51Z"
    - latency: 1.122228ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:51Z"
    - latency: 1.99416ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:51Z"
    - latency: 1.116206ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:51Z"
    - latency: 2.906372ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:28:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.us-west-2.compute.internal
      uid: 3e9f5a70-7b31-4feb-965e-8a8700005731
    resourceVersion: "123556"
    uid: eca61d95-0b8d-486d-8032-d3658ac970e7
  spec:
    sourcePod: network-check-source-6f78d59f99-lskdw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:34:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.001µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 1.832384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:40:51Z"
    - latency: 1.037751ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 1.821084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:39:51Z"
    - latency: 1.30329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 2.041864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:38:51Z"
    - latency: 1.26678ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 1.703786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:37:51Z"
    - latency: 1.139467ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:51Z"
    - latency: 2.335738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:51Z"
kind: List
metadata:
  resourceVersion: ""