apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "19728"
    uid: b71b6856-6a10-43ca-8e08-1e83da368a98
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:31:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 801.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 857.506µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:43:25Z"
    - latency: 902.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:42:25Z"
    - latency: 1.331404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:41:25Z"
    - latency: 809.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:40:25Z"
    - latency: 1.050182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:39:25Z"
    - latency: 771.446µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:38:25Z"
    - latency: 799.093µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:37:25Z"
    - latency: 837.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "20913"
    uid: 9c8cb3cd-6c4e-4c82-a2b9-7e3b408a06d5
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:30:25Z"
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.353188ms
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 7.042241ms
      message: 'load-balancer-api-external: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 6.145329ms
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 8.007666ms
      message: 'load-balancer-api-external: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 5.075981ms
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 8.554086ms
      message: 'load-balancer-api-external: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 3.484094ms
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 6.62896ms
      message: 'load-balancer-api-external: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 4.789706ms
      message: 'load-balancer-api-external: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 9.189056ms
      message: 'load-balancer-api-external: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:44:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "20912"
    uid: e54979d3-99d6-436c-9c4d-c7653b930258
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:30:25Z"
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.289273ms
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 7.07782ms
      message: 'load-balancer-api-internal: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 6.153826ms
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 8.067154ms
      message: 'load-balancer-api-internal: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 5.049344ms
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 8.644534ms
      message: 'load-balancer-api-internal: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 5.016529ms
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 6.603096ms
      message: 'load-balancer-api-internal: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 4.891552ms
      message: 'load-balancer-api-internal: tcp connection to afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 9.231575ms
      message: 'load-balancer-api-internal: resolved host name afaeeba237cb94e829034bef6088f6db-44870034f0e30b19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:44:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-133-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "19726"
    uid: c1a407df-2dd0-47f3-87e3-09bc931282b2
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:31:25Z"
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.359974ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 2.344788ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 2.267619ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:43:25Z"
    - latency: 2.168406ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:42:25Z"
    - latency: 2.910723ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:41:25Z"
    - latency: 2.318591ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:40:25Z"
    - latency: 2.347776ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:39:25Z"
    - latency: 2.401907ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:38:25Z"
    - latency: 2.209785ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:37:25Z"
    - latency: 2.332926ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-137-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "19727"
    uid: 2d7a6331-26e9-467d-9c54-5b9dcb4be886
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:31:25Z"
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.858174ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 1.941314ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 2.086656ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:43:25Z"
    - latency: 2.088035ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:42:25Z"
    - latency: 3.841417ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:41:25Z"
    - latency: 2.166359ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:40:25Z"
    - latency: 1.979966ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:39:25Z"
    - latency: 2.160995ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:38:25Z"
    - latency: 2.227591ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:37:25Z"
    - latency: 2.296022ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-138-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "19725"
    uid: eb7dd507-70f0-4156-9aa7-30fab3512fd6
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:31:25Z"
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.965µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 835.218µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 814.907µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:43:25Z"
    - latency: 715.579µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:42:25Z"
    - latency: 1.893044ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:41:25Z"
    - latency: 1.302461ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:40:25Z"
    - latency: 888.065µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:39:25Z"
    - latency: 1.228602ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:38:25Z"
    - latency: 810.928µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:37:25Z"
    - latency: 745.174µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T05:24:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.ec2.internal
      uid: 1fde88fb-0087-4549-9746-d202575acbd3
    resourceVersion: "20911"
    uid: 62d5747c-9afb-45ce-b1fb-9229aa26ecd7
  spec:
    sourcePod: network-check-source-6f8b768455-9jnhd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T05:30:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.022269ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 1.775881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:48:25Z"
    - latency: 1.072315ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 1.752639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:47:25Z"
    - latency: 1.051922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 1.545898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:46:25Z"
    - latency: 846.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 1.738296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:45:25Z"
    - latency: 823.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:44:25Z"
    - latency: 2.160184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:44:25Z"
kind: List
metadata:
  resourceVersion: ""