apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "69215"
    uid: a41eac46-01b8-4c26-ab19-17b0fe39bdba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:44:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:26:02Z"
    - latency: 1.101646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 1.275983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 6.836415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 1.060407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 965.601µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 1.108331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:20:02Z"
    - latency: 900.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:19:02Z"
    - latency: 1.00298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:02Z"
    - latency: 1.348741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "68142"
    uid: a5d2d9a7-20da-4232-8e70-50f6f65aacd8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:02Z"
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.22526ms
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 8.951121ms
      message: 'load-balancer-api-external: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 5.437621ms
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 8.78227ms
      message: 'load-balancer-api-external: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 5.679816ms
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 24.22287ms
      message: 'load-balancer-api-external: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 4.331279ms
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 8.892001ms
      message: 'load-balancer-api-external: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 4.880295ms
      message: 'load-balancer-api-external: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 7.638242ms
      message: 'load-balancer-api-external: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:21:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "68141"
    uid: fb740126-c8ef-45bf-b4ee-33d827b5de56
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:02Z"
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.22047ms
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 8.988712ms
      message: 'load-balancer-api-internal: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 5.746317ms
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 8.851289ms
      message: 'load-balancer-api-internal: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 5.69593ms
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 24.584253ms
      message: 'load-balancer-api-internal: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 4.718586ms
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 8.950905ms
      message: 'load-balancer-api-internal: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 4.882956ms
      message: 'load-balancer-api-internal: tcp connection to a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 7.649826ms
      message: 'load-balancer-api-internal: resolved host name a96709625fe804496b76ec4bdfb27b87-f6d3e06cfb765ee2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:21:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-network-check-target-ip-10-0-136-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "69214"
    uid: 0e9a5486-f00f-407b-bfd7-b6234710b20b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:44:02Z"
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.290866ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:26:02Z"
    - latency: 2.479374ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 2.470186ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 6.236672ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 2.344983ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 2.924ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 2.35416ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:20:02Z"
    - latency: 2.623155ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:19:02Z"
    - latency: 2.958818ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:02Z"
    - latency: 2.778358ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-network-check-target-ip-10-0-137-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "69213"
    uid: e7ac5d26-eed2-4829-83c1-40300e41497c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:44:02Z"
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.555336ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:26:02Z"
    - latency: 2.09871ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 2.178881ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 4.748448ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 2.299477ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 2.353431ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 2.29737ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:20:02Z"
    - latency: 2.297035ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:19:02Z"
    - latency: 2.24882ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:02Z"
    - latency: 2.09392ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-network-check-target-ip-10-0-143-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "69212"
    uid: 5f14a6bb-f350-45ed-926c-1f8ec312b178
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:44:02Z"
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039156ms
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:26:02Z"
    - latency: 1.305293ms
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 879.145µs
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 5.554914ms
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 1.048213ms
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 1.298878ms
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 961.049µs
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:20:02Z"
    - latency: 790.105µs
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:19:02Z"
    - latency: 916.234µs
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:02Z"
    - latency: 849.947µs
      message: 'network-check-target-ip-10-0-143-245: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-245.ec2.internal
      uid: f8de64b2-47a8-48a5-8c02-27018768307f
    resourceVersion: "68139"
    uid: 06c82d5a-e142-4436-969f-6125c6e654b2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hs78
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 1.913057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:25:02Z"
    - latency: 954.293µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 2.09647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:24:02Z"
    - latency: 1.760894ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 7.635079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:23:02Z"
    - latency: 1.010478ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 2.356631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:22:02Z"
    - latency: 846.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:21:02Z"
    - latency: 1.955964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:21:02Z"
kind: List
metadata:
  resourceVersion: ""