apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64971"
    uid: 5c453612-9374-4933-a315-472b6af8c9a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:31:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 1.327729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 1.049613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 1.197847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 1.421851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 854.419µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:05Z"
    - latency: 883.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:05Z"
    - latency: 1.030437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:05Z"
    - latency: 1.287652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:05Z"
    - latency: 1.194209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64972"
    uid: e7c6d4ce-367d-40a5-94b2-03328aaa6aba
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:05Z"
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.890461ms
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 8.476892ms
      message: 'load-balancer-api-external: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 4.886036ms
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 8.326274ms
      message: 'load-balancer-api-external: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 5.661148ms
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 8.907199ms
      message: 'load-balancer-api-external: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 3.790094ms
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 8.823379ms
      message: 'load-balancer-api-external: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 3.551802ms
      message: 'load-balancer-api-external: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 9.040728ms
      message: 'load-balancer-api-external: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64973"
    uid: 766cd900-4be6-46df-9a0f-496f88aa76bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:05Z"
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.811922ms
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 8.535578ms
      message: 'load-balancer-api-internal: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 4.849126ms
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 8.360481ms
      message: 'load-balancer-api-internal: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 5.555158ms
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 8.94048ms
      message: 'load-balancer-api-internal: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 3.775932ms
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 8.856832ms
      message: 'load-balancer-api-internal: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 3.60118ms
      message: 'load-balancer-api-internal: tcp connection to a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 9.079421ms
      message: 'load-balancer-api-internal: resolved host name a38eab431bd134f36aec01b1146571cd-e595205f10f46837.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-130-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64967"
    uid: 03e3f282-a06f-43df-9c1a-5ebcb8aa4c73
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:31:05Z"
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.117274ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 2.540443ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 2.306473ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 2.631149ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 2.630142ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 2.559082ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:05Z"
    - latency: 2.510198ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:05Z"
    - latency: 3.31917ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:05Z"
    - latency: 2.743577ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:05Z"
    - latency: 2.472497ms
      message: 'network-check-target-ip-10-0-130-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-131-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64969"
    uid: 2d4c9571-4ed0-462e-97dc-f7da6f638226
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:31:05Z"
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.806µs
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 1.048485ms
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 1.549337ms
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 1.150518ms
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 1.655275ms
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 1.168018ms
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:05Z"
    - latency: 953.913µs
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:05Z"
    - latency: 938.242µs
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:05Z"
    - latency: 899.252µs
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:05Z"
    - latency: 988.263µs
      message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-139-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64968"
    uid: e1d6b786-6332-4912-961b-630bd0be8039
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:31:05Z"
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205483ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 2.283222ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 2.470885ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 2.376117ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 2.113121ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 2.196273ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:05Z"
    - latency: 2.217943ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:05Z"
    - latency: 2.309802ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:05Z"
    - latency: 2.699102ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:05Z"
    - latency: 2.470628ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: ce0fe90d-cf7f-4783-86b3-45124daa1523
    resourceVersion: "64970"
    uid: 098ef96e-cc45-47a5-9071-1308bd507539
  spec:
    sourcePod: network-check-source-7d88cb55d8-7c7jv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.34814ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 1.669836ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:05Z"
    - latency: 1.140817ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 1.726829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:05Z"
    - latency: 1.020146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 2.254128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:05Z"
    - latency: 1.611554ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 1.904326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:05Z"
    - latency: 1.634931ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:05Z"
    - latency: 2.034911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:05Z"
kind: List
metadata:
  resourceVersion: ""