apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "70833"
    uid: c716b2ad-4263-4b81-bee9-4f0f6d73fceb
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:41:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.564689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:23:01Z"
    - latency: 1.883836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 927.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 1.011896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 1.2676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 1.149474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 1.493818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:17:01Z"
    - latency: 1.208708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:16:01Z"
    - latency: 850.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:15:01Z"
    - latency: 2.035268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "69836"
    uid: b0a570a1-e3d4-4d29-b7f9-9cf30462c398
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:40:01Z"
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.198885ms
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 8.043495ms
      message: 'load-balancer-api-external: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 4.617846ms
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 6.950497ms
      message: 'load-balancer-api-external: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 6.763801ms
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 7.448143ms
      message: 'load-balancer-api-external: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 4.835229ms
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 8.246295ms
      message: 'load-balancer-api-external: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 2.987135ms
      message: 'load-balancer-api-external: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 9.89242ms
      message: 'load-balancer-api-external: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:18:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "69835"
    uid: 281c1bc6-0869-4491-8242-0d04775aa07a
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:40:01Z"
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.224275ms
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 8.011528ms
      message: 'load-balancer-api-internal: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 4.642603ms
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 6.905047ms
      message: 'load-balancer-api-internal: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 5.903706ms
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 7.610609ms
      message: 'load-balancer-api-internal: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 4.814037ms
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 8.129667ms
      message: 'load-balancer-api-internal: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 5.143566ms
      message: 'load-balancer-api-internal: tcp connection to af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 9.965811ms
      message: 'load-balancer-api-internal: resolved host name af165b06b38b54af1858ea4fe390021d-e4f7a3d53c2f8455.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:18:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-131-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "70831"
    uid: a55bdab6-6cd1-4dab-b3f8-8914dced3905
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:41:01Z"
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.088864ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:23:01Z"
    - latency: 2.220321ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 2.017962ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 2.096607ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 2.106331ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 2.112856ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 2.588111ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:17:01Z"
    - latency: 2.139863ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:16:01Z"
    - latency: 2.127539ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:15:01Z"
    - latency: 3.09397ms
      message: 'network-check-target-ip-10-0-131-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-138-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "70832"
    uid: 35e6a467-f057-4d00-b114-c8ec4af0efba
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:41:01Z"
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.182616ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:23:01Z"
    - latency: 2.355343ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 2.119663ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 1.73169ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 2.111158ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 2.011914ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 2.232182ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:17:01Z"
    - latency: 1.882288ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:16:01Z"
    - latency: 2.364765ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:15:01Z"
    - latency: 2.710539ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-140-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "70830"
    uid: d5f2c4fe-62d2-4011-9594-7fc7e6f676ba
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:41:01Z"
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030169ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:23:01Z"
    - latency: 1.503045ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 1.653438ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 1.036559ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 950.577µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 1.277011ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 1.027922ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:17:01Z"
    - latency: 925.998µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:16:01Z"
    - latency: 1.083291ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:15:01Z"
    - latency: 2.044598ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:34:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: e8a1ba81-2837-4f39-9cf3-68d8bf1ba523
    resourceVersion: "69834"
    uid: 426afb02-ad39-4cbb-91fe-cbf86d2238a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-zkz64
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:40:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 747.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 2.594661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:22:01Z"
    - latency: 834.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 1.736581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:21:01Z"
    - latency: 955.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 2.063491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:20:01Z"
    - latency: 951.209µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 1.969236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:19:01Z"
    - latency: 865.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:18:01Z"
    - latency: 1.943581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:18:01Z"
kind: List
metadata:
  resourceVersion: ""