apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "53769"
    uid: f8daf25c-12d6-48ea-b891-f8c87f9382e4
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:40:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.634869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 1.288764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 1.59604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 836.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 766.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:04:10Z"
    - latency: 1.054297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:10Z"
    - latency: 803.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:10Z"
    - latency: 976.769µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:10Z"
    - latency: 910.626µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:10Z"
    - latency: 1.195888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "54784"
    uid: 46b17c3f-849c-46dd-8d69-604609d43ade
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:39:10Z"
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.668897ms
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 8.69348ms
      message: 'load-balancer-api-external: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 5.673259ms
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 9.416353ms
      message: 'load-balancer-api-external: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 5.016655ms
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 8.970381ms
      message: 'load-balancer-api-external: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 4.116791ms
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 9.070896ms
      message: 'load-balancer-api-external: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 6.40845ms
      message: 'load-balancer-api-external: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 9.731041ms
      message: 'load-balancer-api-external: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "54785"
    uid: 71d2e0ca-ce52-4633-b2d0-3869a6ae6640
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:39:10Z"
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.879301ms
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 8.826373ms
      message: 'load-balancer-api-internal: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 5.646902ms
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 9.63471ms
      message: 'load-balancer-api-internal: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 5.043523ms
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 9.076173ms
      message: 'load-balancer-api-internal: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 4.148274ms
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 8.985094ms
      message: 'load-balancer-api-internal: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 6.37825ms
      message: 'load-balancer-api-internal: tcp connection to a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 9.800143ms
      message: 'load-balancer-api-internal: resolved host name a98b9d7722f8a4692ab5a9b832f782e2-bdc04a22d9dc2bb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-129-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "53766"
    uid: ffde0da5-1021-409a-acd1-7a82a29b047e
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:40:10Z"
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.266043ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 2.594964ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 2.820708ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 2.085526ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 2.290192ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:04:10Z"
    - latency: 2.194786ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:10Z"
    - latency: 2.394012ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:10Z"
    - latency: 2.107269ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:10Z"
    - latency: 1.933036ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:10Z"
    - latency: 2.189675ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-137-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "53768"
    uid: 01574339-4a71-4f6b-9b99-09490bfafa5b
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:40:10Z"
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.166327ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 1.01138ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 715.978µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 1.043823ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 888.742µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:04:10Z"
    - latency: 1.532812ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:10Z"
    - latency: 1.241294ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:10Z"
    - latency: 1.220342ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:10Z"
    - latency: 926.68µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:10Z"
    - latency: 1.209309ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-137-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "53767"
    uid: 28228d1d-6728-4783-bc03-7fc7a9d6ce60
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:40:10Z"
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345016ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 2.214555ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 1.976027ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 2.1664ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 1.780756ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:04:10Z"
    - latency: 2.189418ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:10Z"
    - latency: 1.907556ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:10Z"
    - latency: 2.492586ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:10Z"
    - latency: 1.738756ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:10Z"
    - latency: 1.829364ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:33:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: 53027766-eb13-4836-a6a4-a2a42552e7d7
    resourceVersion: "54783"
    uid: 207f580c-130e-4fa1-a567-9213954c713e
  spec:
    sourcePod: network-check-source-989f8b8dc-m4bxb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:39:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.10135ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 1.529801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:09:10Z"
    - latency: 863.08µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 2.146875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:08:10Z"
    - latency: 833.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 1.818746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:07:10Z"
    - latency: 802.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 2.122636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:06:10Z"
    - latency: 1.451964ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:05:10Z"
    - latency: 1.980236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:05:10Z"
kind: List
metadata:
  resourceVersion: ""