apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "19215"
    uid: ad6766ad-401b-432b-a2a8-047ab0849443
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:48:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 819.874µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 1.058599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:00:04Z"
    - latency: 1.059324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:59:04Z"
    - latency: 791.981µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:58:04Z"
    - latency: 847.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:57:04Z"
    - latency: 950.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:56:04Z"
    - latency: 886.467µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:55:04Z"
    - latency: 1.095393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:54:04Z"
    - latency: 1.112392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "20365"
    uid: 282d6a52-25b5-43fd-b8d1-cafeddfbda64
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:47:04Z"
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.836649ms
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 9.46592ms
      message: 'load-balancer-api-external: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 4.570615ms
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 8.882689ms
      message: 'load-balancer-api-external: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 4.305843ms
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 9.165027ms
      message: 'load-balancer-api-external: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 5.081723ms
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 8.917783ms
      message: 'load-balancer-api-external: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 4.722543ms
      message: 'load-balancer-api-external: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 8.642023ms
      message: 'load-balancer-api-external: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:01:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "20364"
    uid: 0b557bf4-fa33-476b-9f80-fcb4913d0cc4
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:47:04Z"
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.818242ms
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 9.504402ms
      message: 'load-balancer-api-internal: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 4.597744ms
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 8.982562ms
      message: 'load-balancer-api-internal: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 4.269583ms
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 9.135033ms
      message: 'load-balancer-api-internal: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 5.057207ms
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 8.998551ms
      message: 'load-balancer-api-internal: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 5.204226ms
      message: 'load-balancer-api-internal: tcp connection to a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 8.607898ms
      message: 'load-balancer-api-internal: resolved host name a1b7ba6a240e44b72b141d1076f0fbab-0af9f81c8f598e18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:01:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-128-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "19214"
    uid: 377cfdf8-ed9b-475e-bf63-5bc5076a8728
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:48:04Z"
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446268ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 1.966223ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 1.764581ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:00:04Z"
    - latency: 2.268089ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:59:04Z"
    - latency: 2.211821ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:58:04Z"
    - latency: 2.165571ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:57:04Z"
    - latency: 2.200286ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:56:04Z"
    - latency: 2.094924ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:55:04Z"
    - latency: 2.453443ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:54:04Z"
    - latency: 2.169121ms
      message: 'network-check-target-ip-10-0-128-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-131-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "19212"
    uid: 1f49181c-6079-4f69-9464-5dac13a229e9
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:48:04Z"
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260743ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 2.225545ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 1.947776ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:00:04Z"
    - latency: 2.348105ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:59:04Z"
    - latency: 2.139856ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:58:04Z"
    - latency: 2.247436ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:57:04Z"
    - latency: 2.419054ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:56:04Z"
    - latency: 2.192817ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:55:04Z"
    - latency: 2.769288ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:54:04Z"
    - latency: 2.14339ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-134-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "19213"
    uid: 67ec7659-01d3-4062-a67c-73ccda3f8c15
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:48:04Z"
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.337533ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 757.303µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 811.229µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:00:04Z"
    - latency: 1.006535ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:59:04Z"
    - latency: 1.420093ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:58:04Z"
    - latency: 991.026µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:57:04Z"
    - latency: 847.038µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:56:04Z"
    - latency: 1.288444ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:55:04Z"
    - latency: 926.691µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:54:04Z"
    - latency: 981.521µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T05:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T05:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: 8088c4c1-d33c-425d-bd8f-af1126da52b4
    resourceVersion: "20363"
    uid: ae68fb3e-c0a4-4516-bb77-54e4ab158285
  spec:
    sourcePod: network-check-source-65bdbbff45-7fxm9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T05:47:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.733µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 1.539261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:05:04Z"
    - latency: 852.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 1.439948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:04:04Z"
    - latency: 882.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 1.933068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:03:04Z"
    - latency: 1.054238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 1.655594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:02:04Z"
    - latency: 899.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T06:01:04Z"
    - latency: 1.631079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T06:01:04Z"
kind: List
metadata:
  resourceVersion: ""