apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "162756"
    uid: 854514a9-cb7f-4e0b-8259-cdfb4412089b
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 1.615407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 1.012745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 1.180944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:15:57Z"
    - latency: 1.121778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:14:57Z"
    - latency: 1.185738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:13:57Z"
    - latency: 1.268448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:12:57Z"
    - latency: 1.12973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:11:57Z"
    - latency: 945.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:57Z"
    - latency: 1.222748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "165643"
    uid: 8ee9841b-8433-4156-93a2-66db370c87bb
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:14:57Z"
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.819707ms
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 8.146725ms
      message: 'load-balancer-api-external: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 17.939459ms
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 6.537555ms
      message: 'load-balancer-api-external: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 16.906809ms
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 7.485206ms
      message: 'load-balancer-api-external: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 19.149349ms
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 13.229629ms
      message: 'load-balancer-api-external: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 16.33682ms
      message: 'load-balancer-api-external: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 9.945173ms
      message: 'load-balancer-api-external: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:16:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "165644"
    uid: f48f626b-2c02-4a60-9631-65dabd4aa92d
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:14:57Z"
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.928878ms
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 8.075242ms
      message: 'load-balancer-api-internal: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 17.925167ms
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 6.56017ms
      message: 'load-balancer-api-internal: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 17.40547ms
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 7.435416ms
      message: 'load-balancer-api-internal: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 18.657225ms
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 13.283481ms
      message: 'load-balancer-api-internal: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 16.518154ms
      message: 'load-balancer-api-internal: tcp connection to aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 9.960451ms
      message: 'load-balancer-api-internal: resolved host name aa3c5a5c38cf948468e820704411ff38-518de883913ca346.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:16:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-network-check-target-ip-10-0-130-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "162752"
    uid: e439c0bb-4a5c-42a8-9533-da6f40a42416
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:57Z"
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.485209ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 2.253506ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 2.145583ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 2.496091ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:15:57Z"
    - latency: 2.128154ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:14:57Z"
    - latency: 2.329901ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:13:57Z"
    - latency: 2.198586ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:12:57Z"
    - latency: 2.418268ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:11:57Z"
    - latency: 2.281907ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:57Z"
    - latency: 2.26065ms
      message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-network-check-target-ip-10-0-135-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "162754"
    uid: dc5035d1-ff22-446d-a0c7-012fb279ac81
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:57Z"
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.521305ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 2.614875ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 2.108179ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 2.555737ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:15:57Z"
    - latency: 2.459361ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:14:57Z"
    - latency: 2.700619ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:13:57Z"
    - latency: 2.377421ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:12:57Z"
    - latency: 2.935826ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:11:57Z"
    - latency: 2.176373ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:57Z"
    - latency: 2.350384ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-network-check-target-ip-10-0-142-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "162751"
    uid: 2a119a7e-7dd7-42f2-844e-2addb735f6d4
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:57Z"
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150273ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 1.177925ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 1.000351ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 1.038254ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:15:57Z"
    - latency: 1.499165ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:14:57Z"
    - latency: 1.219666ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:13:57Z"
    - latency: 1.024133ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:12:57Z"
    - latency: 1.086444ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:11:57Z"
    - latency: 973.067µs
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:57Z"
    - latency: 1.603912ms
      message: 'network-check-target-ip-10-0-142-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:08:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-185-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-185.ec2.internal
      uid: c29427d7-bee5-4f3c-8490-686d9f732e2e
    resourceVersion: "165642"
    uid: 77c63660-3433-435b-8a21-0248c94c71dd
  spec:
    sourcePod: network-check-source-6f78d59f99-9xdrk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:14:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 2.27685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:20:57Z"
    - latency: 837.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 1.678431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:19:57Z"
    - latency: 1.087878ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 1.952277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:18:57Z"
    - latency: 1.018404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 1.847696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:17:57Z"
    - latency: 1.192814ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:16:57Z"
    - latency: 2.177562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:16:57Z"
kind: List
metadata:
  resourceVersion: ""