apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "21382"
    uid: e69b07b3-ab08-48de-9bf4-d0d7d488efd9
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:29:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.745µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:03Z"
    - latency: 1.162402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:03Z"
    - latency: 854.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:03Z"
    - latency: 873.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 872.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 1.027219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 839.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 987.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 827.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:03Z"
    - latency: 1.200865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "20041"
    uid: 45c2371a-1dd1-42a6-9a09-e220964394c6
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:03Z"
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.669884ms
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 8.32248ms
      message: 'load-balancer-api-external: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 6.056057ms
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 13.865756ms
      message: 'load-balancer-api-external: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 5.32832ms
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 7.889706ms
      message: 'load-balancer-api-external: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 5.241147ms
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 8.792326ms
      message: 'load-balancer-api-external: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 5.379833ms
      message: 'load-balancer-api-external: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 13.585426ms
      message: 'load-balancer-api-external: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:36:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "20040"
    uid: bb44a3e4-321f-4fc5-a28c-3156cb997631
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:03Z"
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.082464ms
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 8.419109ms
      message: 'load-balancer-api-internal: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 6.081539ms
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 13.829381ms
      message: 'load-balancer-api-internal: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 5.312622ms
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 7.99967ms
      message: 'load-balancer-api-internal: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 5.229792ms
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 8.873086ms
      message: 'load-balancer-api-internal: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 6.337794ms
      message: 'load-balancer-api-internal: tcp connection to a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 13.708477ms
      message: 'load-balancer-api-internal: resolved host name a306fa385e8d24b1a91690710c39cea1-4fa5cc76128c466f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:36:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-network-check-target-ip-10-0-134-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "21380"
    uid: eb0cfade-c9ef-419f-9a3d-ef17c98d182a
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:29:03Z"
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.2042ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:03Z"
    - latency: 2.280564ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:03Z"
    - latency: 2.231535ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:03Z"
    - latency: 2.301477ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 2.323474ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 2.355622ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 2.418676ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 2.198181ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 2.019118ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:03Z"
    - latency: 2.36093ms
      message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-network-check-target-ip-10-0-140-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "21379"
    uid: 1255fc4c-bca1-44ce-917f-88cb0e7ec9ec
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:29:03Z"
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.176µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:03Z"
    - latency: 1.283276ms
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:03Z"
    - latency: 1.24969ms
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:03Z"
    - latency: 1.080646ms
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 882.294µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 915.149µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 1.24095ms
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 886.184µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 807.231µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:03Z"
    - latency: 904.818µs
      message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-network-check-target-ip-10-0-141-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "21381"
    uid: 4026ce23-56f7-49de-be98-ec8dcc40bfc3
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:29:03Z"
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.619569ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:03Z"
    - latency: 2.716252ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:03Z"
    - latency: 2.304822ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:03Z"
    - latency: 2.568735ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 2.377638ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 2.567741ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 2.365828ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 2.520432ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 2.398807ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:03Z"
    - latency: 2.366854ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:22:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-1.ec2.internal
      uid: 3698faa6-5617-4a69-a958-1c1f99895fe6
    resourceVersion: "20039"
    uid: 9f0ac972-4f27-493f-a1ab-fe8a37cb2bfa
  spec:
    sourcePod: network-check-source-989f8b8dc-zt5xg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.655µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 1.719517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:03Z"
    - latency: 886.234µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 1.654776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:03Z"
    - latency: 849.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 1.766826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:03Z"
    - latency: 1.144486ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 1.756943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:03Z"
    - latency: 855.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:03Z"
    - latency: 1.910449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:36:03Z"
kind: List
metadata:
  resourceVersion: ""