apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "26101"
    uid: ce8e4731-a352-44b7-828d-6b299e4ff4b5
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:28:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 862.672µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 1.061715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 1.103685ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:46:03Z"
    - latency: 973.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:45:03Z"
    - latency: 909.895µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:44:03Z"
    - latency: 1.037071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:43:03Z"
    - latency: 947.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:42:03Z"
    - latency: 1.067247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:41:03Z"
    - latency: 1.030653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:40:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "27042"
    uid: 468d54c5-49bd-433b-9fca-15e5814ef91a
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:27:03Z"
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.387838ms
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 8.733823ms
      message: 'load-balancer-api-external: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 5.234668ms
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 8.086638ms
      message: 'load-balancer-api-external: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 4.010999ms
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 10.003006ms
      message: 'load-balancer-api-external: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 5.790498ms
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 7.650693ms
      message: 'load-balancer-api-external: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 4.517182ms
      message: 'load-balancer-api-external: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 7.985931ms
      message: 'load-balancer-api-external: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "27043"
    uid: 906f9b56-33f4-48fd-83df-fbb623e1c542
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:27:03Z"
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.391611ms
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 8.697853ms
      message: 'load-balancer-api-internal: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 5.254611ms
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 8.044143ms
      message: 'load-balancer-api-internal: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 4.150697ms
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 10.066911ms
      message: 'load-balancer-api-internal: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 5.223167ms
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 7.608393ms
      message: 'load-balancer-api-internal: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 6.593075ms
      message: 'load-balancer-api-internal: tcp connection to ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 7.896634ms
      message: 'load-balancer-api-internal: resolved host name ac40c68b22f904ca8b0828d0405dc25d-915a39820882e986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-136-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "26100"
    uid: 14fd3d1a-8fad-43ba-a691-9c47b229830f
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:28:03Z"
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.233246ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 2.288713ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 2.470762ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 2.587127ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:46:03Z"
    - latency: 2.186043ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:45:03Z"
    - latency: 2.060688ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:44:03Z"
    - latency: 2.48975ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:43:03Z"
    - latency: 1.968922ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:42:03Z"
    - latency: 2.324671ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:41:03Z"
    - latency: 2.499798ms
      message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:40:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-137-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "26099"
    uid: 906b5fa5-c013-44c3-9f3c-9a309b8f1e47
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:28:03Z"
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289224ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 2.211355ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 2.157923ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 2.089809ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:46:03Z"
    - latency: 2.16175ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:45:03Z"
    - latency: 2.182091ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:44:03Z"
    - latency: 2.379558ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:43:03Z"
    - latency: 2.267739ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:42:03Z"
    - latency: 2.158717ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:41:03Z"
    - latency: 2.463229ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:40:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-141-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "26098"
    uid: b2081b58-2ffb-45a5-ba93-ecde164d84b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:28:03Z"
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.353µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 1.14942ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 841.512µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 936.226µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:46:03Z"
    - latency: 917.35µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:45:03Z"
    - latency: 905.968µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:44:03Z"
    - latency: 868.52µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:43:03Z"
    - latency: 744.555µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:42:03Z"
    - latency: 771.614µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:41:03Z"
    - latency: 868.295µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:40:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:21:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: 63901859-eb8a-4fcd-bd90-a21933b01285
    resourceVersion: "27041"
    uid: f542db4e-b518-499b-9435-60561cd08daf
  spec:
    sourcePod: network-check-source-7d88cb55d8-mrznf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:27:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32835ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 1.695761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:51:03Z"
    - latency: 824.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 1.762632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:50:03Z"
    - latency: 1.317402ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 1.874456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:49:03Z"
    - latency: 1.153832ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 1.848342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:48:03Z"
    - latency: 747.093µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:47:03Z"
    - latency: 1.664926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:47:03Z"
kind: List
metadata:
  resourceVersion: ""