apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "38437"
    uid: 49735dcb-d045-4f04-8a14-c29b356cc08b
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:20:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:47Z"
    - latency: 1.067991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:47Z"
    - latency: 1.027673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:47Z"
    - latency: 926.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:47Z"
    - latency: 797.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:47Z"
    - latency: 1.293594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:47Z"
    - latency: 824.64µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:47Z"
    - latency: 790.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:47Z"
    - latency: 1.072999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:54:47Z"
    - latency: 984.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "41324"
    uid: 67994779-dcdc-4449-abf5-be4bbd662c97
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:19:47Z"
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.807633ms
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 7.070237ms
      message: 'load-balancer-api-external: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 5.154165ms
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 6.897865ms
      message: 'load-balancer-api-external: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 3.986225ms
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 6.319041ms
      message: 'load-balancer-api-external: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 10.490632ms
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 6.908568ms
      message: 'load-balancer-api-external: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 7.589209ms
      message: 'load-balancer-api-external: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:47Z"
    - latency: 6.695145ms
      message: 'load-balancer-api-external: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "41325"
    uid: 2be29d05-3d19-4acd-926d-494fda2d2848
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:19:47Z"
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.759069ms
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 7.165926ms
      message: 'load-balancer-api-internal: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 5.182712ms
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 6.846824ms
      message: 'load-balancer-api-internal: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 7.651436ms
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 6.387698ms
      message: 'load-balancer-api-internal: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 4.307066ms
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 6.832338ms
      message: 'load-balancer-api-internal: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 16.908021ms
      message: 'load-balancer-api-internal: tcp connection to ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:47Z"
    - latency: 6.739988ms
      message: 'load-balancer-api-internal: resolved host name ad0cdfe0e326f45b5aa1b566eebc3a10-76fd29d5fe107923.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-129-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "38436"
    uid: 4a916811-c1f1-479b-8323-e09ef849a581
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:20:47Z"
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.210465ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:47Z"
    - latency: 2.311751ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:47Z"
    - latency: 2.176929ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:47Z"
    - latency: 2.10308ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:47Z"
    - latency: 2.158696ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:47Z"
    - latency: 2.275418ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:47Z"
    - latency: 2.20166ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:47Z"
    - latency: 2.215585ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:47Z"
    - latency: 2.180299ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:54:47Z"
    - latency: 2.193848ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "38434"
    uid: e8391362-df33-49f1-9dd4-22067b3aac21
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:20:47Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422622ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:47Z"
    - latency: 2.641724ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:47Z"
    - latency: 2.375105ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:47Z"
    - latency: 2.60113ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:47Z"
    - latency: 2.379017ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:47Z"
    - latency: 2.161414ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:47Z"
    - latency: 2.271847ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:47Z"
    - latency: 2.274361ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:47Z"
    - latency: 2.808222ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:54:47Z"
    - latency: 2.13618ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-137-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "38435"
    uid: 31552fb3-c394-470d-bc3a-eb0b9de4fd6e
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:20:47Z"
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.350179ms
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:47Z"
    - latency: 1.54255ms
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:47Z"
    - latency: 829.225µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:47Z"
    - latency: 955.993µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:47Z"
    - latency: 1.5662ms
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:47Z"
    - latency: 1.577701ms
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:47Z"
    - latency: 789.088µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:47Z"
    - latency: 835.413µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:47Z"
    - latency: 798.829µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:54:47Z"
    - latency: 742.344µs
      message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:13:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-8.ec2.internal
      uid: 929abfd4-574e-4cfa-acb3-699f95062c26
    resourceVersion: "41323"
    uid: b4c31f12-ee3d-489f-983a-114aadd21a09
  spec:
    sourcePod: network-check-source-685456655f-rv5xr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:19:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 1.713558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:07:47Z"
    - latency: 978.368µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 1.580214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:06:47Z"
    - latency: 1.244107ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 1.71219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:05:47Z"
    - latency: 5.861795ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 1.701285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:47Z"
    - latency: 780.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:47Z"
    - latency: 1.698222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:47Z"
kind: List
metadata:
  resourceVersion: ""