apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184991"
    uid: 39b83b20-244f-484f-9e48-ae4ae1125d1c
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11: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.799263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 1.008091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 1.201867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 1.303514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 1.177675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 965.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:23:37Z"
    - latency: 1.17521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:22:37Z"
    - latency: 1.384347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:21:37Z"
    - latency: 1.159812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:37Z"
    - latency: 1.345201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184992"
    uid: 5089bea6-c7f0-4f4a-9249-86e3374d0f1f
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:10:37Z"
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.937573ms
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 8.622009ms
      message: 'load-balancer-api-external: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 15.892494ms
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 8.527279ms
      message: 'load-balancer-api-external: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 17.84083ms
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 6.979219ms
      message: 'load-balancer-api-external: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 19.035857ms
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 7.31923ms
      message: 'load-balancer-api-external: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 17.518743ms
      message: 'load-balancer-api-external: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 6.572036ms
      message: 'load-balancer-api-external: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:24:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184993"
    uid: 1e5e02f6-b52c-4198-a9dc-a500ecb01910
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:10:37Z"
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.308367ms
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 8.580883ms
      message: 'load-balancer-api-internal: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 18.920442ms
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 8.538311ms
      message: 'load-balancer-api-internal: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 18.365755ms
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 6.998922ms
      message: 'load-balancer-api-internal: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 16.800403ms
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 7.348293ms
      message: 'load-balancer-api-internal: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 17.510606ms
      message: 'load-balancer-api-internal: tcp connection to a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 6.646066ms
      message: 'load-balancer-api-internal: resolved host name a78c045a7c98c483f9b286696453a865-1125b8a5de198092.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:24:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-134-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184986"
    uid: 5f5d670c-dd96-4a36-aa2d-282ab11e5a85
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:37Z"
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.505481ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 2.689421ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 2.444426ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 2.363917ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 2.655987ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 2.325082ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:23:37Z"
    - latency: 2.249989ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:22:37Z"
    - latency: 2.053463ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:21:37Z"
    - latency: 2.045639ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:37Z"
    - latency: 2.326212ms
      message: 'network-check-target-ip-10-0-134-92: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-135-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184989"
    uid: fc7d6943-063f-4a85-94d2-11f4884aea51
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:37Z"
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.981µs
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 1.017996ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 1.014488ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 1.028981ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 1.242402ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 975.593µs
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:23:37Z"
    - latency: 859.323µs
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:22:37Z"
    - latency: 1.01151ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:21:37Z"
    - latency: 1.345172ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:37Z"
    - latency: 1.056364ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-136-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184987"
    uid: 31d5db06-d6d0-4bb0-8da6-a1358af1179b
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:37Z"
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.142809ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 1.856392ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 2.107494ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 2.406116ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 2.256691ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 1.904524ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:23:37Z"
    - latency: 2.099032ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:22:37Z"
    - latency: 2.029774ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:21:37Z"
    - latency: 2.007329ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:37Z"
    - latency: 2.171512ms
      message: 'network-check-target-ip-10-0-136-97: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:04:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-226-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-226.ec2.internal
      uid: 3a67be34-720a-4abb-8c73-f2946cc5cb7c
    resourceVersion: "184990"
    uid: 64e63af7-b418-48ae-a9af-80c12b8aa50b
  spec:
    sourcePod: network-check-source-6f78d59f99-zn99v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:10:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.187014ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 2.673264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:28:37Z"
    - latency: 1.050072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 1.965567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:27:37Z"
    - latency: 953.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 1.697839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:26:37Z"
    - latency: 1.016862ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 1.930584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:25:37Z"
    - latency: 986.321µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:24:37Z"
    - latency: 1.82143ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:24:37Z"
kind: List
metadata:
  resourceVersion: ""