apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32082"
    uid: ae016038-8a03-4004-8139-a59de67a83b3
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.812348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 1.006724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 1.241039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 1.299739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 1.229152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 1.416486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:20:20Z"
    - latency: 1.613819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:19:20Z"
    - latency: 1.499243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:18:20Z"
    - latency: 805.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:17:20Z"
    - latency: 1.1061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32084"
    uid: cf77cc72-32c4-4788-888b-2f196384703a
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:20Z"
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.395668ms
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 9.603051ms
      message: 'load-balancer-api-external: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 5.080845ms
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 8.70683ms
      message: 'load-balancer-api-external: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 5.738824ms
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 8.631688ms
      message: 'load-balancer-api-external: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 5.421934ms
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 8.524252ms
      message: 'load-balancer-api-external: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 4.424145ms
      message: 'load-balancer-api-external: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 10.85393ms
      message: 'load-balancer-api-external: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:21:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32083"
    uid: 96c31a45-e469-4c9e-b7ec-3bbb6ac2a340
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:20Z"
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.299346ms
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 9.570488ms
      message: 'load-balancer-api-internal: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 5.064607ms
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 8.79722ms
      message: 'load-balancer-api-internal: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 5.72652ms
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 8.697311ms
      message: 'load-balancer-api-internal: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 6.929484ms
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 8.441495ms
      message: 'load-balancer-api-internal: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 8.825265ms
      message: 'load-balancer-api-internal: tcp connection to a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 10.8397ms
      message: 'load-balancer-api-internal: resolved host name a46349be9dc664878a51962766c457ac-7011a0af1489d6fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:21:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-128-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32080"
    uid: f7998029-20ae-4ccc-891a-ba568431ad11
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:20Z"
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223203ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 2.005393ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 2.201659ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 2.3003ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 2.344534ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 2.361991ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:20:20Z"
    - latency: 2.299659ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:19:20Z"
    - latency: 2.330495ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:18:20Z"
    - latency: 2.175195ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:17:20Z"
    - latency: 2.358333ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-133-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32078"
    uid: 5f0b90df-41a0-42d3-a70b-2280846d4f69
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:20Z"
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.377µs
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 1.281792ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 927.478µs
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 1.675665ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 1.477435ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 1.716565ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:20:20Z"
    - latency: 859.48µs
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:19:20Z"
    - latency: 1.743207ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:18:20Z"
    - latency: 1.57614ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:17:20Z"
    - latency: 1.156105ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-140-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32079"
    uid: 504f3a76-810e-441e-ae77-c85570b57ab3
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:20Z"
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.31898ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 2.298572ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 2.737319ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 2.253367ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 2.156434ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 2.048335ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:20:20Z"
    - latency: 2.220585ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:19:20Z"
    - latency: 2.178329ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:18:20Z"
    - latency: 2.228691ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:17:20Z"
    - latency: 2.113576ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:43:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-99.ec2.internal
      uid: 5a36cc36-af08-47b3-8a59-f5ebe6e7d3cd
    resourceVersion: "32081"
    uid: c704bcdb-1c39-40f4-a762-c9a78105f98b
  spec:
    sourcePod: network-check-source-6f8b768455-qn2k4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.102292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 2.52346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:25:20Z"
    - latency: 1.239084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 1.842869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:24:20Z"
    - latency: 997.2µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 1.855262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:23:20Z"
    - latency: 1.541641ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 1.8619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:22:20Z"
    - latency: 937.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:20Z"
    - latency: 1.823425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:21:20Z"
kind: List
metadata:
  resourceVersion: ""