apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "171073"
    uid: 40a8df3b-2065-4b2e-b4b0-a871adefe6ef
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:40:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.752887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 1.84834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 1.403175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 1.426576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:40:28Z"
    - latency: 1.197674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:39:28Z"
    - latency: 1.433434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:38:28Z"
    - latency: 2.432124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:37:28Z"
    - latency: 980.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:36:28Z"
    - latency: 1.707927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:35:28Z"
    - latency: 2.116271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "176527"
    uid: fdd1a4c7-c99b-4611-a531-762ebfd282c8
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:39:28Z"
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.511114ms
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 8.402853ms
      message: 'load-balancer-api-external: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 19.053969ms
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 7.178567ms
      message: 'load-balancer-api-external: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 16.878271ms
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 15.848332ms
      message: 'load-balancer-api-external: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 16.390615ms
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 10.266419ms
      message: 'load-balancer-api-external: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 18.162147ms
      message: 'load-balancer-api-external: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 10.742974ms
      message: 'load-balancer-api-external: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:41:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "176529"
    uid: 8df40fd4-b1d3-43b4-8d84-1818187736f5
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:39:28Z"
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.617498ms
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 8.505331ms
      message: 'load-balancer-api-internal: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 15.063308ms
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 7.054673ms
      message: 'load-balancer-api-internal: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 30.00555ms
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 15.284271ms
      message: 'load-balancer-api-internal: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 15.969731ms
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 10.324376ms
      message: 'load-balancer-api-internal: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 16.312222ms
      message: 'load-balancer-api-internal: tcp connection to a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 10.726157ms
      message: 'load-balancer-api-internal: resolved host name a7551c75c1f7e45bf8140a2923b63656-a3c1e5a51f2a777e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:41:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-142-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "171072"
    uid: 829319d4-32ae-485e-bea6-45910c3edcd8
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:40:28Z"
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.113412ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 2.335581ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 1.617656ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 2.064676ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:40:28Z"
    - latency: 1.093725ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:39:28Z"
    - latency: 1.92338ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:38:28Z"
    - latency: 1.754415ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:37:28Z"
    - latency: 1.047849ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:36:28Z"
    - latency: 1.493752ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:35:28Z"
    - latency: 3.020061ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-142-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "171071"
    uid: ffe3cdc2-f8e5-44b6-bdfa-0a157bb45c03
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:40:28Z"
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.810016ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 3.601953ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 2.732024ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 7.146267ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:40:28Z"
    - latency: 2.154085ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:39:28Z"
    - latency: 3.181993ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:38:28Z"
    - latency: 4.484104ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:37:28Z"
    - latency: 2.62775ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:36:28Z"
    - latency: 2.847022ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:35:28Z"
    - latency: 3.526583ms
      message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-143-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "171070"
    uid: f8db68ef-d9c1-4f31-bb41-87f51cf8ca0c
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:40:28Z"
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.494986ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 3.764643ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 2.870113ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 2.700282ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:40:28Z"
    - latency: 2.483424ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:39:28Z"
    - latency: 3.20976ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:38:28Z"
    - latency: 3.226218ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:37:28Z"
    - latency: 2.59707ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:36:28Z"
    - latency: 3.085811ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:35:28Z"
    - latency: 2.762947ms
      message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:33:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: d087a313-29a6-4266-9f5f-1664fb0ec129
    resourceVersion: "176526"
    uid: c9fd46ce-983e-400f-a07e-913b45ccc518
  spec:
    sourcePod: network-check-source-6f78d59f99-7jfl7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T11:39:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218607ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 2.601436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:45:28Z"
    - latency: 1.607708ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 2.027866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:44:28Z"
    - latency: 1.160315ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 7.863301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:43:28Z"
    - latency: 1.442963ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 9.046232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:42:28Z"
    - latency: 1.024744ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:41:28Z"
    - latency: 5.958885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:41:28Z"
kind: List
metadata:
  resourceVersion: ""