apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "53759"
    uid: 6374a6b6-3812-4727-9c26-da3a74518e68
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:20:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.885µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 980.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 1.07114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 960.196µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 987.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:06Z"
    - latency: 1.326495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:06Z"
    - latency: 991.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:06Z"
    - latency: 978.238µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:41:06Z"
    - latency: 1.08816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:40:06Z"
    - latency: 1.016138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "54761"
    uid: b8c9b8b2-cf78-41e4-8c6b-18cc85caa2b6
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:19:06Z"
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.556044ms
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 6.553654ms
      message: 'load-balancer-api-external: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 5.426921ms
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 6.630672ms
      message: 'load-balancer-api-external: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 6.018799ms
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 7.747656ms
      message: 'load-balancer-api-external: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 5.458869ms
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 9.288055ms
      message: 'load-balancer-api-external: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 9.177611ms
      message: 'load-balancer-api-external: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 6.15953ms
      message: 'load-balancer-api-external: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "54759"
    uid: 6783fa8e-5422-4539-8b5e-8eb729f9e951
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:19:06Z"
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.15574ms
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 6.50061ms
      message: 'load-balancer-api-internal: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 5.409605ms
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 6.672109ms
      message: 'load-balancer-api-internal: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 5.427302ms
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 7.71321ms
      message: 'load-balancer-api-internal: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 5.376598ms
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 9.360804ms
      message: 'load-balancer-api-internal: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 9.162256ms
      message: 'load-balancer-api-internal: tcp connection to ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 6.20742ms
      message: 'load-balancer-api-internal: resolved host name ab5ddf437116d400fa8df3fd78957b0a-911b3c4e67c01cd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-network-check-target-ip-10-0-132-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "53757"
    uid: b790c796-74fa-4027-a5a2-a11762fa442b
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:20:06Z"
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234993ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 2.645469ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 2.247004ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 2.378016ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 2.365745ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:06Z"
    - latency: 2.264802ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:06Z"
    - latency: 2.547177ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:06Z"
    - latency: 2.24643ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:41:06Z"
    - latency: 2.87592ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:40:06Z"
    - latency: 2.340053ms
      message: 'network-check-target-ip-10-0-132-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-network-check-target-ip-10-0-140-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "53756"
    uid: 8e9e39cc-8415-4131-b19c-f158b8c54c51
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:20:06Z"
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.81µs
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 960.348µs
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 1.059189ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 918.679µs
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 1.329094ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:06Z"
    - latency: 1.328959ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:06Z"
    - latency: 997.729µs
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:06Z"
    - latency: 1.498098ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:41:06Z"
    - latency: 1.275687ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:40:06Z"
    - latency: 1.316983ms
      message: 'network-check-target-ip-10-0-140-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-network-check-target-ip-10-0-142-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "53758"
    uid: aa058bed-9330-43db-8e61-33510711f5c7
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:20:06Z"
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.121392ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 2.511884ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 2.622518ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 2.132757ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 2.474571ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:06Z"
    - latency: 2.293877ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:06Z"
    - latency: 2.224202ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:06Z"
    - latency: 2.533031ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:41:06Z"
    - latency: 2.314921ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:40:06Z"
    - latency: 2.580564ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-82.ec2.internal
      uid: a49019d9-82ee-4971-8138-1840efb93365
    resourceVersion: "54757"
    uid: 5c62b2ba-4e1a-4c47-9ef6-2c607e7f3ff4
  spec:
    sourcePod: network-check-source-989f8b8dc-ptfwd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:19:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 772.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 1.614008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:06Z"
    - latency: 883.559µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 1.87765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:06Z"
    - latency: 1.542855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 2.04718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:47:06Z"
    - latency: 1.239699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 1.974395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:46:06Z"
    - latency: 878.243µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:06Z"
    - latency: 1.777109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:45:06Z"
kind: List
metadata:
  resourceVersion: ""