apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53480"
    uid: 5959957c-a0dd-49e1-920d-6c4f428872c0
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:21:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.601288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 1.034974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 943.973µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 1.065127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 974.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 1.016927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:31Z"
    - latency: 875.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:31Z"
    - latency: 1.444464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:31Z"
    - latency: 1.001055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:31Z"
    - latency: 1.043749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53481"
    uid: ecc54727-18cc-4746-8527-5bbdc30e5038
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:31Z"
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.63132ms
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 7.77448ms
      message: 'load-balancer-api-external: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 5.308275ms
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 6.639298ms
      message: 'load-balancer-api-external: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 4.564215ms
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 7.519602ms
      message: 'load-balancer-api-external: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 4.458946ms
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 7.602055ms
      message: 'load-balancer-api-external: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 5.509156ms
      message: 'load-balancer-api-external: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 7.705115ms
      message: 'load-balancer-api-external: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53482"
    uid: eb1bfb83-d92d-4d02-ae28-3c30ab25b5bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:31Z"
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.597489ms
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 7.857208ms
      message: 'load-balancer-api-internal: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 4.880782ms
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 6.596618ms
      message: 'load-balancer-api-internal: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 4.593395ms
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 7.479058ms
      message: 'load-balancer-api-internal: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 4.503638ms
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 7.628274ms
      message: 'load-balancer-api-internal: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 5.545734ms
      message: 'load-balancer-api-internal: tcp connection to ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 7.742898ms
      message: 'load-balancer-api-internal: resolved host name ab1e13555fb794cd0bb5c4444791fe7e-5dc820c40115c5b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-139-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53479"
    uid: d7e68b11-0f5f-4637-89a6-cbd458aa5c10
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:21:31Z"
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.469549ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 2.156339ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 2.26752ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 2.289465ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 2.216539ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 1.979581ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:31Z"
    - latency: 2.19213ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:31Z"
    - latency: 2.47877ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:31Z"
    - latency: 2.484516ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:31Z"
    - latency: 2.547885ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-142-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53476"
    uid: 2663a2de-af68-4330-a2b3-4dc1583cc7cb
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:21:31Z"
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.569366ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 885.141µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 1.49678ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 1.483735ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 1.193419ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 1.221264ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:31Z"
    - latency: 781.117µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:31Z"
    - latency: 1.305868ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:31Z"
    - latency: 893.912µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:31Z"
    - latency: 1.755877ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-143-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53478"
    uid: fe2bbb6e-870a-4ee1-86e7-f1dbb7f3886b
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:21:31Z"
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.481781ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 1.995905ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 2.044729ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 1.831615ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 2.184718ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 2.219155ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:31Z"
    - latency: 1.822562ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:31Z"
    - latency: 2.466381ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:31Z"
    - latency: 1.868934ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:31Z"
    - latency: 2.217118ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:14:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: 8f47b58c-e03e-4ccd-b3a5-e5279729a1e9
    resourceVersion: "53477"
    uid: 7746838c-54cc-4538-a0ec-05481ccab932
  spec:
    sourcePod: network-check-source-7d88cb55d8-cswxb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017027ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 1.893324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:38:31Z"
    - latency: 880.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 1.70822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:37:31Z"
    - latency: 1.180736ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 2.171803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:31Z"
    - latency: 826.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 2.44197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:31Z"
    - latency: 1.375425ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:31Z"
    - latency: 2.380348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:31Z"
kind: List
metadata:
  resourceVersion: ""