apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "51782"
    uid: 7d6a4bd8-70ae-4c3b-a9e9-80d5dae1d849
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:45:37Z"
    - latency: 1.04505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:44:37Z"
    - latency: 981.33µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:43:37Z"
    - latency: 1.226342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:42:37Z"
    - latency: 875.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:41:37Z"
    - latency: 1.015525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:40:37Z"
    - latency: 1.073408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:39:37Z"
    - latency: 1.014809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:37Z"
    - latency: 1.498532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:37Z"
    - latency: 1.30754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "55054"
    uid: c671ebe6-e306-4eba-a70c-9e60eb6b86c3
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:37Z"
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.332094ms
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 11.108272ms
      message: 'load-balancer-api-external: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 4.050785ms
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 8.321758ms
      message: 'load-balancer-api-external: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 4.261806ms
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 8.314185ms
      message: 'load-balancer-api-external: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 4.967745ms
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 8.477132ms
      message: 'load-balancer-api-external: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 4.809631ms
      message: 'load-balancer-api-external: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:46:37Z"
    - latency: 7.758978ms
      message: 'load-balancer-api-external: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:46:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "55055"
    uid: d6b7f901-4510-478c-908d-a00da3c2b918
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:37Z"
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.799387ms
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 11.037061ms
      message: 'load-balancer-api-internal: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 4.022829ms
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 8.420332ms
      message: 'load-balancer-api-internal: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 4.232766ms
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 8.225964ms
      message: 'load-balancer-api-internal: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 3.892245ms
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 8.532058ms
      message: 'load-balancer-api-internal: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 4.784609ms
      message: 'load-balancer-api-internal: tcp connection to a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:46:37Z"
    - latency: 7.691051ms
      message: 'load-balancer-api-internal: resolved host name a43607ca76424452c9872c8733a08993-4886c2fefa398ee6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:46:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-network-check-target-ip-10-0-129-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "51779"
    uid: 1de5e848-91e8-4dd4-b066-3bc4fcd069c8
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:37Z"
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 721.748µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:45:37Z"
    - latency: 915.022µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:44:37Z"
    - latency: 997.261µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:43:37Z"
    - latency: 967.863µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:42:37Z"
    - latency: 773.38µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:41:37Z"
    - latency: 825.661µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:40:37Z"
    - latency: 954.434µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:39:37Z"
    - latency: 1.25485ms
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:37Z"
    - latency: 1.405525ms
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:37Z"
    - latency: 822.086µs
      message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-network-check-target-ip-10-0-133-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "51781"
    uid: 1819d5b8-c194-43ce-8ae9-394bc6eb1dea
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:37Z"
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192796ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:45:37Z"
    - latency: 2.202005ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:44:37Z"
    - latency: 2.266409ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:43:37Z"
    - latency: 1.932017ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:42:37Z"
    - latency: 2.131151ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:41:37Z"
    - latency: 2.16315ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:40:37Z"
    - latency: 2.090649ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:39:37Z"
    - latency: 2.124458ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:37Z"
    - latency: 2.200854ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:37Z"
    - latency: 2.209742ms
      message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-network-check-target-ip-10-0-134-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "51780"
    uid: cecf1754-0ac2-4e66-917b-d073fece651e
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:37Z"
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.704099ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:45:37Z"
    - latency: 2.005305ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:44:37Z"
    - latency: 1.982187ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:43:37Z"
    - latency: 1.664926ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:42:37Z"
    - latency: 2.043024ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:41:37Z"
    - latency: 1.964317ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:40:37Z"
    - latency: 1.905289ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:39:37Z"
    - latency: 1.880523ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:37Z"
    - latency: 2.01393ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:37Z"
    - latency: 2.162893ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-4.ec2.internal
      uid: ec81ad10-0ee2-420f-b66b-034a9f86de33
    resourceVersion: "55053"
    uid: e5144970-45ca-43d0-b8b2-40843f9b056e
  spec:
    sourcePod: network-check-source-8894fc9bd-rfr4p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.24µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 1.56728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:50:37Z"
    - latency: 1.178809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 1.681352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:49:37Z"
    - latency: 950.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 1.568877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:48:37Z"
    - latency: 853.735µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 1.898914ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:47:37Z"
    - latency: 1.100668ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:46:37Z"
    - latency: 1.756114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:46:37Z"
kind: List
metadata:
  resourceVersion: ""