apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33052"
    uid: f527b088-829b-48d0-b7d7-9fab0aadd99d
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:23:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 1.074862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 917.992µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 980.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 1.109962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 1.080979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:19Z"
    - latency: 975.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:52:19Z"
    - latency: 1.025989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:51:19Z"
    - latency: 1.261382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:50:19Z"
    - latency: 1.00353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:49:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33053"
    uid: 9bc9e8ad-e454-4a09-b166-852f8dda2524
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:22:19Z"
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.768048ms
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 9.073016ms
      message: 'load-balancer-api-external: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 5.698908ms
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 8.370143ms
      message: 'load-balancer-api-external: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 8.163942ms
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 8.320131ms
      message: 'load-balancer-api-external: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 6.083926ms
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 9.057101ms
      message: 'load-balancer-api-external: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 7.10545ms
      message: 'load-balancer-api-external: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 8.141061ms
      message: 'load-balancer-api-external: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33054"
    uid: a2c656ea-2ee8-40ff-9014-22e8314b612d
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:22:19Z"
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.258578ms
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 9.026599ms
      message: 'load-balancer-api-internal: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 5.697895ms
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 8.443427ms
      message: 'load-balancer-api-internal: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 3.554164ms
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 8.242155ms
      message: 'load-balancer-api-internal: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 6.096855ms
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 8.931256ms
      message: 'load-balancer-api-internal: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 7.059712ms
      message: 'load-balancer-api-internal: tcp connection to a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 8.168265ms
      message: 'load-balancer-api-internal: resolved host name a26f6cc49a32a4582ac20560abd4a4c7-e09e8493dac2997f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-network-check-target-ip-10-0-130-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33049"
    uid: fb621db3-9a40-4679-bf78-8e651cdf828b
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:23:19Z"
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.361441ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 2.25278ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 2.365359ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 2.286892ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 1.995055ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 2.188728ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:19Z"
    - latency: 2.147271ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:52:19Z"
    - latency: 2.261873ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:51:19Z"
    - latency: 2.350414ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:50:19Z"
    - latency: 2.059393ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:49:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-network-check-target-ip-10-0-130-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33048"
    uid: 6cd4c3c6-7c02-4eb9-8923-280e982bcef4
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:23:19Z"
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019665ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 1.311945ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 953.768µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 753.294µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 881.382µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 850.259µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:19Z"
    - latency: 1.139614ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:52:19Z"
    - latency: 923.464µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:51:19Z"
    - latency: 1.55286ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:50:19Z"
    - latency: 812.802µs
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:49:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-network-check-target-ip-10-0-138-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33050"
    uid: 8177fa9a-2c04-4b49-ba95-e204d3505557
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:23:19Z"
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205449ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 2.161673ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 2.219205ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 2.789634ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 2.149344ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 2.204859ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:19Z"
    - latency: 2.44474ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:52:19Z"
    - latency: 2.286943ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:51:19Z"
    - latency: 1.904451ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:50:19Z"
    - latency: 2.184143ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:49:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:16:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-152.ec2.internal
      uid: 1f6a2ce3-80e5-40b8-9f7f-6c136e3aaa00
    resourceVersion: "33051"
    uid: 2e1768df-2dc9-4332-97fc-5eb76680e744
  spec:
    sourcePod: network-check-source-989f8b8dc-bshp7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:22:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.322445ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 1.929221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:58:19Z"
    - latency: 828.951µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 1.719924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:57:19Z"
    - latency: 911.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 1.68384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:56:19Z"
    - latency: 1.202296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 1.730023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:55:19Z"
    - latency: 785.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:19Z"
    - latency: 1.840634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:54:19Z"
kind: List
metadata:
  resourceVersion: ""