apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63121"
    uid: e6eeefb5-c6ea-4e82-a81b-6bbdb00a7a6c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:34:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.227103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 1.011357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 1.153514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 1.24183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 1.022667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 1.090424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:04:55Z"
    - latency: 1.30002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:03:55Z"
    - latency: 1.112926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:02:55Z"
    - latency: 1.18577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:01:55Z"
    - latency: 1.208004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:00:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63123"
    uid: efcad6d8-ce66-4f85-859d-20fbc2c1d837
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:33:55Z"
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.166653ms
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 6.957029ms
      message: 'load-balancer-api-external: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 3.492545ms
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 8.880808ms
      message: 'load-balancer-api-external: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 4.645116ms
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 8.101429ms
      message: 'load-balancer-api-external: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 5.581179ms
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 7.212306ms
      message: 'load-balancer-api-external: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 9.279125ms
      message: 'load-balancer-api-external: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 6.666064ms
      message: 'load-balancer-api-external: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:05:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63122"
    uid: 0b6df1c2-ad06-4c83-8900-8c06455729e7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:33:55Z"
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267158ms
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 7.052602ms
      message: 'load-balancer-api-internal: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 3.508137ms
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 8.849657ms
      message: 'load-balancer-api-internal: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 4.897456ms
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 8.185842ms
      message: 'load-balancer-api-internal: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 5.183704ms
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 7.121925ms
      message: 'load-balancer-api-internal: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 5.549906ms
      message: 'load-balancer-api-internal: tcp connection to a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 6.644412ms
      message: 'load-balancer-api-internal: resolved host name a08ef12f5bc0d4e958ef14159a27ac25-253f7ebe4f52eb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:05:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-132-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63117"
    uid: bc51c0ce-6e1b-4cbb-99e5-c26391cb82d8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:34:55Z"
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.756µs
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 1.09877ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 1.222656ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 912.218µs
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 935.676µs
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 1.106704ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:04:55Z"
    - latency: 1.855309ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:03:55Z"
    - latency: 967.039µs
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:02:55Z"
    - latency: 856.12µs
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:01:55Z"
    - latency: 1.4835ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:00:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-141-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63120"
    uid: ae18bf9b-d609-4941-a04a-685e3c3ae5ce
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:34:55Z"
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.547355ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 2.214018ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 2.051774ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 2.004293ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 2.268164ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 2.25483ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:04:55Z"
    - latency: 2.52981ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:03:55Z"
    - latency: 2.048428ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:02:55Z"
    - latency: 2.295525ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:01:55Z"
    - latency: 2.30886ms
      message: 'network-check-target-ip-10-0-141-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:00:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-142-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63118"
    uid: 7a2df3dd-678e-4a06-8912-2e27e818f864
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:34:55Z"
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.988052ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 1.663355ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 2.031628ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 1.754823ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 2.034955ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 1.860411ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:04:55Z"
    - latency: 2.453162ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:03:55Z"
    - latency: 2.030096ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:02:55Z"
    - latency: 2.030471ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:01:55Z"
    - latency: 1.744087ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:00:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T16:27:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-151.ec2.internal
      uid: b77415f0-8b53-445e-b85b-9e3b2779989f
    resourceVersion: "63119"
    uid: 576b345c-abb2-487c-96db-3605398d459c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-t66gt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T16:33:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 1.77389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:09:55Z"
    - latency: 1.117986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 1.658762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:08:55Z"
    - latency: 860.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 1.704248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:07:55Z"
    - latency: 1.08953ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 1.739795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:06:55Z"
    - latency: 1.100861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T17:05:55Z"
    - latency: 1.856197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T17:05:55Z"
kind: List
metadata:
  resourceVersion: ""