apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38801"
    uid: 8e6d528c-f7ea-49ec-95e1-d1d7df42181b
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:05:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:47:28Z"
    - latency: 981.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 825.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 806.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 1.201688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 941.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 1.057303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:41:28Z"
    - latency: 841.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:40:28Z"
    - latency: 776.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:39:28Z"
    - latency: 1.018902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:38:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38268"
    uid: f41bd474-5253-40af-bad6-4606c0e4337d
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:04:28Z"
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.796657ms
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 8.234553ms
      message: 'load-balancer-api-external: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 6.353442ms
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 9.089908ms
      message: 'load-balancer-api-external: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 5.795442ms
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 8.360817ms
      message: 'load-balancer-api-external: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 5.112723ms
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 9.053716ms
      message: 'load-balancer-api-external: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 4.914637ms
      message: 'load-balancer-api-external: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 7.663008ms
      message: 'load-balancer-api-external: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:42:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38267"
    uid: a5a292dc-a0d3-4a75-b820-90ba945920bd
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:04:28Z"
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.75505ms
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 8.31397ms
      message: 'load-balancer-api-internal: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 6.309155ms
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 9.134619ms
      message: 'load-balancer-api-internal: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 4.703806ms
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 8.322466ms
      message: 'load-balancer-api-internal: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 4.52474ms
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 9.14819ms
      message: 'load-balancer-api-internal: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 4.937513ms
      message: 'load-balancer-api-internal: tcp connection to aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 7.544017ms
      message: 'load-balancer-api-internal: resolved host name aa5587bd9a44a465f9bf0b20b6ef07c7-0d86d1eb291b029a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:42:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-131-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38799"
    uid: e9dc1514-38ce-421e-8462-76a28d6b9a61
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:05:28Z"
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422515ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:47:28Z"
    - latency: 2.295205ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 2.532502ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 2.438415ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 2.248742ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 2.599181ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 2.31283ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:41:28Z"
    - latency: 1.88781ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:40:28Z"
    - latency: 2.045457ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:39:28Z"
    - latency: 2.245421ms
      message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:38:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-132-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38798"
    uid: 3d0e22e3-1e04-4fa9-8902-02ac566b8502
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:05:28Z"
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.842µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:47:28Z"
    - latency: 763.468µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 749.447µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 692.632µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 823.377µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 1.330626ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 753.161µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:41:28Z"
    - latency: 765.895µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:40:28Z"
    - latency: 751.904µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:39:28Z"
    - latency: 769.444µs
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:38:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-135-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38800"
    uid: 700a21fb-76db-46ad-a85d-b2c216824e06
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:05:28Z"
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.294655ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:47:28Z"
    - latency: 2.298586ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 2.614412ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 2.283716ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 2.242392ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 2.459346ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 2.438438ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:41:28Z"
    - latency: 2.452703ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:40:28Z"
    - latency: 2.087756ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:39:28Z"
    - latency: 1.965093ms
      message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:38:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-226-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-226.ec2.internal
      uid: 9f359faa-06f3-49d9-b34e-b2c45006ff6d
    resourceVersion: "38266"
    uid: 252db7ff-e16c-48fd-ad5d-578c2d71034a
  spec:
    sourcePod: network-check-source-685456655f-bxjtn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:04:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 1.863971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:46:28Z"
    - latency: 977.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 2.732476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:45:28Z"
    - latency: 885.79µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 1.758481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:44:28Z"
    - latency: 1.189307ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 1.974262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:43:28Z"
    - latency: 1.724501ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:42:28Z"
    - latency: 1.644969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:42:28Z"
kind: List
metadata:
  resourceVersion: ""