apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "16928"
    uid: c487063f-0bcc-41ac-a8e3-04d825586c21
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:02:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 1.304478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:08:29Z"
    - latency: 1.411965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:07:29Z"
    - latency: 1.028184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:06:29Z"
    - latency: 979.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:29Z"
    - latency: 1.223551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:29Z"
    - latency: 1.065482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:29Z"
    - latency: 952.951µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:29Z"
    - latency: 1.040184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:29Z"
    - latency: 1.055443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "19124"
    uid: ffb06cb4-4a2a-465c-a179-f4f96dc3b7a7
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:01:29Z"
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.103829ms
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 7.423827ms
      message: 'load-balancer-api-external: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 4.232793ms
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 7.292171ms
      message: 'load-balancer-api-external: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 4.236409ms
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 10.002745ms
      message: 'load-balancer-api-external: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 5.760887ms
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 8.320308ms
      message: 'load-balancer-api-external: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 6.302777ms
      message: 'load-balancer-api-external: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 8.45906ms
      message: 'load-balancer-api-external: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:09:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "19123"
    uid: 01c3d7e8-7727-4d32-8cf8-822ee12238d9
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:01:29Z"
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.071313ms
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 7.459473ms
      message: 'load-balancer-api-internal: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 4.216839ms
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 7.220448ms
      message: 'load-balancer-api-internal: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 4.22762ms
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 10.069157ms
      message: 'load-balancer-api-internal: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 4.693123ms
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 8.226753ms
      message: 'load-balancer-api-internal: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 6.291777ms
      message: 'load-balancer-api-internal: tcp connection to a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 8.40666ms
      message: 'load-balancer-api-internal: resolved host name a54429ee7208d4d868b9958099ca06b3-1f6aeb39155a62e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:09:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-network-check-target-ip-10-0-133-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "16927"
    uid: 3163d823-6acb-41b8-b904-10508e659473
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:02:29Z"
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.187781ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 2.008428ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:08:29Z"
    - latency: 2.228385ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:07:29Z"
    - latency: 1.961478ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:06:29Z"
    - latency: 2.172907ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:29Z"
    - latency: 2.192696ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:29Z"
    - latency: 2.317624ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:29Z"
    - latency: 2.359308ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:29Z"
    - latency: 2.248446ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:29Z"
    - latency: 2.420198ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-network-check-target-ip-10-0-140-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "16925"
    uid: 985934d8-c1b6-48f5-8909-62e099b9581f
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:02:29Z"
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.297089ms
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 838.315µs
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:08:29Z"
    - latency: 1.620657ms
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:07:29Z"
    - latency: 1.28578ms
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:06:29Z"
    - latency: 1.02246ms
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:29Z"
    - latency: 942.857µs
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:29Z"
    - latency: 936.945µs
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:29Z"
    - latency: 929.614µs
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:29Z"
    - latency: 1.071642ms
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:29Z"
    - latency: 831.596µs
      message: 'network-check-target-ip-10-0-140-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-network-check-target-ip-10-0-142-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "16926"
    uid: 3e312665-053e-43a7-8492-d11b6f02ebfb
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:02:29Z"
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236621ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 2.463554ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:08:29Z"
    - latency: 1.816355ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:07:29Z"
    - latency: 1.999079ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:06:29Z"
    - latency: 1.932906ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:29Z"
    - latency: 1.778017ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:29Z"
    - latency: 1.933352ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:29Z"
    - latency: 2.164024ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:29Z"
    - latency: 2.042936ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:29Z"
    - latency: 1.944445ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:55:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-189.ec2.internal
      uid: 6afdeac4-8f16-49ec-8bd1-d9485e5245ca
    resourceVersion: "19122"
    uid: 7931cfc6-3c97-453d-aee4-f89dd7eeafb8
  spec:
    sourcePod: network-check-source-7cbc45fddc-m8cxx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T03:01:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.386µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 1.781255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:13:29Z"
    - latency: 1.186333ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 1.511295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:12:29Z"
    - latency: 860.719µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 1.769104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:11:29Z"
    - latency: 1.47686ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 1.905343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:10:29Z"
    - latency: 1.017909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:09:29Z"
    - latency: 1.711638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:09:29Z"
kind: List
metadata:
  resourceVersion: ""