apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "54151"
    uid: 3ebd5596-a9a2-4099-ae9d-31d4ee06e8a2
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:13:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 782.133µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 1.017246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 1.499013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 1.145919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:02Z"
    - latency: 1.031029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:02Z"
    - latency: 1.306184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:02Z"
    - latency: 1.072784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:02Z"
    - latency: 1.094417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:02Z"
    - latency: 1.189287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "55084"
    uid: b8ec9636-a530-4c0d-9963-bd6c5c9393ba
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:12:02Z"
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.15904ms
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 6.570568ms
      message: 'load-balancer-api-external: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 5.360157ms
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 6.42246ms
      message: 'load-balancer-api-external: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 3.79661ms
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 6.701452ms
      message: 'load-balancer-api-external: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 5.522909ms
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 6.436345ms
      message: 'load-balancer-api-external: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 6.191781ms
      message: 'load-balancer-api-external: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 7.745078ms
      message: 'load-balancer-api-external: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "55083"
    uid: 1674114a-2dfd-4e87-86d8-b649bb6850b7
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:12:02Z"
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.069214ms
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 6.59767ms
      message: 'load-balancer-api-internal: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 5.408303ms
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 6.507685ms
      message: 'load-balancer-api-internal: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 3.836805ms
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 6.782886ms
      message: 'load-balancer-api-internal: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 5.461612ms
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 6.519655ms
      message: 'load-balancer-api-internal: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 6.17859ms
      message: 'load-balancer-api-internal: tcp connection to ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 7.813524ms
      message: 'load-balancer-api-internal: resolved host name ad9cc3ddf5bf24d3d80f0b332ae50bc1-439c3deb719ae0da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-network-check-target-ip-10-0-128-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "54148"
    uid: c195e016-3b09-4070-a6c9-7d5c181a33f9
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:13:02Z"
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.28µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 1.113534ms
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 1.593669ms
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 968.314µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 1.261649ms
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:02Z"
    - latency: 907.993µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:02Z"
    - latency: 1.672406ms
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:02Z"
    - latency: 899.843µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:02Z"
    - latency: 850.117µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:02Z"
    - latency: 855.162µs
      message: 'network-check-target-ip-10-0-128-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-network-check-target-ip-10-0-135-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "54150"
    uid: c9be2696-fe7a-4431-bbbe-44c56829c0bf
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:13:02Z"
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.115194ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 1.921034ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 1.951063ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 1.988516ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 1.904861ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:02Z"
    - latency: 2.000283ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:02Z"
    - latency: 1.946682ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:02Z"
    - latency: 1.942553ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:02Z"
    - latency: 1.803507ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:02Z"
    - latency: 2.20877ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-network-check-target-ip-10-0-141-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "54149"
    uid: ae1b6147-d440-4e0a-8fe3-cfec1ab086ce
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:13:02Z"
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192766ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 2.312659ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 2.190562ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 2.274374ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 1.964601ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:02Z"
    - latency: 2.149007ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:02Z"
    - latency: 2.698631ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:02Z"
    - latency: 2.212651ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:02Z"
    - latency: 2.083948ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:02Z"
    - latency: 2.140078ms
      message: 'network-check-target-ip-10-0-141-217: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-39.ec2.internal
      uid: cbb7b27d-03f7-40d3-b177-6d76f1c7357e
    resourceVersion: "55082"
    uid: ba568a7b-694b-4594-b32b-3f734f6024e1
  spec:
    sourcePod: network-check-source-869dcfcdcd-7n55h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:12:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 1.550717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:42:02Z"
    - latency: 818.929µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 1.751474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:41:02Z"
    - latency: 947.325µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 1.758246ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:02Z"
    - latency: 858.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 1.813572ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:02Z"
    - latency: 825.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:02Z"
    - latency: 2.524167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:02Z"
kind: List
metadata:
  resourceVersion: ""