apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "32815"
    uid: 819f1d36-46c3-4491-a0cf-8ed959e9d246
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.646686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 1.316807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 957.59µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 1.131992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:47:26Z"
    - latency: 991.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:26Z"
    - latency: 3.01256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:26Z"
    - latency: 1.183163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:26Z"
    - latency: 1.095176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:26Z"
    - latency: 1.136001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:26Z"
    - latency: 933.484µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "34108"
    uid: 40630ffa-2c0b-4851-ba9f-d6825ddd0384
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:26Z"
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.593932ms
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 9.711071ms
      message: 'load-balancer-api-external: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 15.940764ms
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 7.651005ms
      message: 'load-balancer-api-external: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 15.501233ms
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 11.902649ms
      message: 'load-balancer-api-external: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 16.930608ms
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 7.967244ms
      message: 'load-balancer-api-external: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 17.641175ms
      message: 'load-balancer-api-external: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 7.776117ms
      message: 'load-balancer-api-external: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "34109"
    uid: 6c9220b5-cda8-421b-81a1-8ed9d8d6b247
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:26Z"
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.526355ms
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 9.6178ms
      message: 'load-balancer-api-internal: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 22.333427ms
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 7.690685ms
      message: 'load-balancer-api-internal: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 17.21139ms
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 11.754072ms
      message: 'load-balancer-api-internal: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 16.916417ms
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 8.100074ms
      message: 'load-balancer-api-internal: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 17.10012ms
      message: 'load-balancer-api-internal: tcp connection to a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 7.745405ms
      message: 'load-balancer-api-internal: resolved host name a9c6bc033741d43fbb900995d9543326-1387338057e92d6c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:48:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-network-check-target-ip-10-0-131-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "32812"
    uid: 033625cb-c267-4d79-b20a-1f253bbf5376
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:26Z"
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.265886ms
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 1.262626ms
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 1.270047ms
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 803.282µs
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:47:26Z"
    - latency: 910.774µs
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:26Z"
    - latency: 3.155119ms
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:26Z"
    - latency: 830.024µs
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:26Z"
    - latency: 900.897µs
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:26Z"
    - latency: 822.34µs
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:26Z"
    - latency: 1.274583ms
      message: 'network-check-target-ip-10-0-131-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "32814"
    uid: 61739db8-ff49-4c6b-b46a-14df9ab985fe
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:26Z"
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.989222ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 2.00144ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 1.821341ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 2.204805ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:47:26Z"
    - latency: 2.054397ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:26Z"
    - latency: 3.643009ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:26Z"
    - latency: 1.837012ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:26Z"
    - latency: 1.971926ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:26Z"
    - latency: 1.886524ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:26Z"
    - latency: 2.14541ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-network-check-target-ip-10-0-143-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "32813"
    uid: de330b27-2b8f-42e8-bf08-6ee6f51b1a13
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:26Z"
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.218452ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 2.622916ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 2.254949ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 2.634809ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:47:26Z"
    - latency: 2.198031ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:26Z"
    - latency: 3.896853ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:26Z"
    - latency: 2.177139ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:26Z"
    - latency: 2.515851ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:26Z"
    - latency: 2.249687ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:26Z"
    - latency: 2.29759ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-175-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-175.ec2.internal
      uid: 14094085-6aa9-4aa4-a942-54f97c0d8858
    resourceVersion: "34107"
    uid: c98e8905-4a0f-40db-b1e2-e318d1d2bb4e
  spec:
    sourcePod: network-check-source-6f78d59f99-k9mfw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.304µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 2.448996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:52:26Z"
    - latency: 822.054µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 1.843525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:51:26Z"
    - latency: 770.974µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 3.02937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:50:26Z"
    - latency: 943.499µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 1.859184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:49:26Z"
    - latency: 962.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:48:26Z"
    - latency: 1.783608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:48:26Z"
kind: List
metadata:
  resourceVersion: ""