apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "74627"
    uid: ee42a7ad-33ea-48d7-8b7f-08c81158c45c
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:44:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.720123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 13.335366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 1.468253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 1.382435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:44Z"
    - latency: 1.641586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:44Z"
    - latency: 2.153209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:44Z"
    - latency: 1.510675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:44Z"
    - latency: 17.46782ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:44Z"
    - latency: 16.846614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:44Z"
    - latency: 1.310921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "79722"
    uid: b4795c3e-552d-4255-96c1-712fe3826d62
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:43:44Z"
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 21.060666ms
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 8.960905ms
      message: 'load-balancer-api-external: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 17.990189ms
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 9.267012ms
      message: 'load-balancer-api-external: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 26.676555ms
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 32.52931ms
      message: 'load-balancer-api-external: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 29.564096ms
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 34.795722ms
      message: 'load-balancer-api-external: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 17.67285ms
      message: 'load-balancer-api-external: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 9.40814ms
      message: 'load-balancer-api-external: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "79724"
    uid: a14a1d74-fb3b-4b5a-8243-01a28298b181
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:43:44Z"
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 86.818156ms
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 8.921307ms
      message: 'load-balancer-api-internal: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 16.803638ms
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 9.375563ms
      message: 'load-balancer-api-internal: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 27.063144ms
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 35.332758ms
      message: 'load-balancer-api-internal: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 29.10459ms
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 34.23092ms
      message: 'load-balancer-api-internal: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 16.507185ms
      message: 'load-balancer-api-internal: tcp connection to afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 9.624096ms
      message: 'load-balancer-api-internal: resolved host name afddaa9ce96414bb899a9dbb8ea36aa3-d0bc0f9066e19f32.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-network-check-target-ip-10-0-129-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "74625"
    uid: e105234a-bb14-4ad8-9b8d-62ad229de171
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:44:44Z"
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.342151ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 33.898781ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 3.812367ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 2.652684ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:44Z"
    - latency: 2.64577ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:44Z"
    - latency: 4.819651ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:44Z"
    - latency: 2.973296ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:44Z"
    - latency: 16.946563ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:44Z"
    - latency: 18.273028ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:44Z"
    - latency: 2.541188ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-network-check-target-ip-10-0-137-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "74618"
    uid: 05a74f4a-21bb-4cdb-a911-bb40dc45e9dc
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:44:44Z"
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.494945ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 12.631246ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 2.677819ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 2.407813ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:44Z"
    - latency: 2.664288ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:44Z"
    - latency: 2.421709ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:44Z"
    - latency: 2.641335ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:44Z"
    - latency: 187.284321ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:44Z"
    - latency: 17.764452ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:44Z"
    - latency: 2.324689ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-network-check-target-ip-10-0-142-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "74613"
    uid: ab21fc7b-8898-4f21-bf72-8f219010d7b2
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:44:44Z"
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.365832ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 13.225413ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 1.860329ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 1.220598ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:02:44Z"
    - latency: 1.970887ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:01:44Z"
    - latency: 1.51149ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:00:44Z"
    - latency: 1.297745ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:59:44Z"
    - latency: 17.62245ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:58:44Z"
    - latency: 33.182878ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:57:44Z"
    - latency: 1.59952ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:56:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:37:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-36.ec2.internal
      uid: e68695a5-03c8-4069-9a30-b471253d4dc7
    resourceVersion: "79721"
    uid: fa3129e1-cbdc-421f-8683-fe443c690708
  spec:
    sourcePod: network-check-source-6f78d59f99-gzkb8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:43:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.581616ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 1.972539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:07:44Z"
    - latency: 1.22581ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 2.555144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:06:44Z"
    - latency: 7.185487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 11.404306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:05:44Z"
    - latency: 2.137428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 15.484083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:04:44Z"
    - latency: 1.059378ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:03:44Z"
    - latency: 2.326267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:03:44Z"
kind: List
metadata:
  resourceVersion: ""