apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "54685"
    uid: a427f791-0c5c-4dee-8b00-63a0c94e25d0
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.117948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:08Z"
    - latency: 798.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:08Z"
    - latency: 1.311702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:08Z"
    - latency: 1.136756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:08Z"
    - latency: 987.958µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:08Z"
    - latency: 776.653µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 955.443µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 1.138229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 788.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 877.798µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "49882"
    uid: aa11cf30-0b07-425e-b0e9-51926c884c46
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:08Z"
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.312538ms
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 8.357211ms
      message: 'load-balancer-api-external: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 3.382137ms
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 8.58072ms
      message: 'load-balancer-api-external: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 5.344994ms
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 8.235785ms
      message: 'load-balancer-api-external: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 4.202675ms
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 8.378852ms
      message: 'load-balancer-api-external: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 4.998335ms
      message: 'load-balancer-api-external: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
    - latency: 7.939089ms
      message: 'load-balancer-api-external: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "49881"
    uid: d3760780-175c-449f-ada2-2631acc58f38
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:08Z"
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.062846ms
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 8.447911ms
      message: 'load-balancer-api-internal: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 3.365545ms
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 8.541959ms
      message: 'load-balancer-api-internal: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 3.682787ms
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 8.277783ms
      message: 'load-balancer-api-internal: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 3.69747ms
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 8.416019ms
      message: 'load-balancer-api-internal: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 5.049848ms
      message: 'load-balancer-api-internal: tcp connection to af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
    - latency: 7.916953ms
      message: 'load-balancer-api-internal: resolved host name af04e660d504444478946c8a2f1caf78-4cdd45aeeaaecae0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-132-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "54684"
    uid: ec5859f9-e3f8-49a3-91fb-623a43fb7130
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:08Z"
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.413758ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:08Z"
    - latency: 2.575107ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:08Z"
    - latency: 2.385666ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:08Z"
    - latency: 2.338791ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:08Z"
    - latency: 2.207287ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:08Z"
    - latency: 2.304321ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 2.50995ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 2.341215ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 2.727952ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 2.232403ms
      message: 'network-check-target-ip-10-0-132-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-135-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "54683"
    uid: 064a0d92-4fc3-4a3e-8b4f-68499aab14c4
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:08Z"
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950867ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:08Z"
    - latency: 2.182243ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:08Z"
    - latency: 2.261075ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:08Z"
    - latency: 2.324153ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:08Z"
    - latency: 1.956667ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:08Z"
    - latency: 2.622686ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 2.443591ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 2.05503ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 2.196567ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 2.335296ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-141-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "54682"
    uid: 24c72d25-9fb6-4682-b8c2-94a7fabf42a6
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:08Z"
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 719.464µs
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:08Z"
    - latency: 1.431015ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:08Z"
    - latency: 992.99µs
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:08Z"
    - latency: 849.615µs
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:08Z"
    - latency: 850.078µs
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:08Z"
    - latency: 1.368755ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 1.423578ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 1.036264ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 1.469276ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 873.385µs
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-134.ec2.internal
      uid: 94f921e3-4e12-40f8-8a83-bb6f539e9c78
    resourceVersion: "49879"
    uid: bf4b612b-6b9a-4c63-87fe-323a4a7121bc
  spec:
    sourcePod: network-check-source-989f8b8dc-9z8f4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 1.746953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:06:08Z"
    - latency: 1.033109ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 1.600135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:05:08Z"
    - latency: 819.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 1.62479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:04:08Z"
    - latency: 840.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 1.719393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:03:08Z"
    - latency: 798.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:08Z"
    - latency: 1.793862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:02:08Z"
kind: List
metadata:
  resourceVersion: ""