apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "43159"
    uid: fef9f30d-2b8c-4499-9889-b723fe07e287
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:36:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.717µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 975.804µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 1.145756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 1.02802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:54:52Z"
    - latency: 930.419µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:53:52Z"
    - latency: 939.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:52:52Z"
    - latency: 882.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:51:52Z"
    - latency: 1.105852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:50:52Z"
    - latency: 917.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:49:52Z"
    - latency: 1.048495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "45518"
    uid: 2e273577-8922-4044-8a75-74ab774c6ad8
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:35:52Z"
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.420812ms
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 14.568674ms
      message: 'load-balancer-api-external: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 4.807754ms
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 8.192763ms
      message: 'load-balancer-api-external: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 3.552845ms
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 7.890029ms
      message: 'load-balancer-api-external: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 4.154761ms
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 10.937881ms
      message: 'load-balancer-api-external: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 4.911282ms
      message: 'load-balancer-api-external: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 7.480923ms
      message: 'load-balancer-api-external: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "45517"
    uid: 5b48e8c6-6051-4b88-86d3-9dd291cb2150
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:35:52Z"
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.30292ms
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 14.544639ms
      message: 'load-balancer-api-internal: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 4.788847ms
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 8.054035ms
      message: 'load-balancer-api-internal: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 3.512816ms
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 7.968583ms
      message: 'load-balancer-api-internal: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 3.542604ms
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 10.897923ms
      message: 'load-balancer-api-internal: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 4.919096ms
      message: 'load-balancer-api-internal: tcp connection to a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 7.51558ms
      message: 'load-balancer-api-internal: resolved host name a6209fb5d0a104d6195594c7efea3b39-f01a06cf95217e45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-128-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "43158"
    uid: 78c99211-c754-4dd7-ae56-db06c5a45c06
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:36:52Z"
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.398625ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 2.216706ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 2.149239ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 2.322628ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:54:52Z"
    - latency: 2.45433ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:53:52Z"
    - latency: 1.854427ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:52:52Z"
    - latency: 2.516508ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:51:52Z"
    - latency: 2.229502ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:50:52Z"
    - latency: 2.96014ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:49:52Z"
    - latency: 2.254433ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-141-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "43154"
    uid: c530a83d-2e8a-437b-bc44-5f722a78e9bf
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:36:52Z"
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286314ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 1.413522ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 767.984µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 956.743µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:54:52Z"
    - latency: 834.115µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:53:52Z"
    - latency: 860.806µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:52:52Z"
    - latency: 800.326µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:51:52Z"
    - latency: 870.143µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:50:52Z"
    - latency: 1.504442ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:49:52Z"
    - latency: 876.657µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-143-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "43156"
    uid: 78980d7d-049d-4a68-99db-52148a1ce83f
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:36:52Z"
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.615457ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 2.587651ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 2.399486ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 2.369222ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:54:52Z"
    - latency: 2.209046ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:53:52Z"
    - latency: 2.153027ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:52:52Z"
    - latency: 1.813468ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:51:52Z"
    - latency: 2.461767ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:50:52Z"
    - latency: 2.545316ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:49:52Z"
    - latency: 2.397237ms
      message: 'network-check-target-ip-10-0-143-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:29:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: cbbdc3f0-c808-4b48-ad23-bd79b4422d1d
    resourceVersion: "45515"
    uid: bda5c931-813b-4bef-8254-e3b699ce8c29
  spec:
    sourcePod: network-check-source-7f44b6dd87-vcphj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:35:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 1.81657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:59:52Z"
    - latency: 1.249343ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 1.607069ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:58:52Z"
    - latency: 954.087µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 1.680668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:57:52Z"
    - latency: 977.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 1.911724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:56:52Z"
    - latency: 813.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T21:55:52Z"
    - latency: 1.61114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T21:55:52Z"
kind: List
metadata:
  resourceVersion: ""