apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "53352"
    uid: 6733acfd-13bc-4721-ae8a-9d320d272c9f
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:37:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.266355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 1.744801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 1.088831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 956.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 1.073989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:24Z"
    - latency: 1.25218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:24Z"
    - latency: 1.474103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:24Z"
    - latency: 1.284527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:24Z"
    - latency: 977.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:24Z"
    - latency: 947.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "54233"
    uid: 505e3791-8150-4e18-946e-16a99ad35816
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:36:24Z"
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.670481ms
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 7.656495ms
      message: 'load-balancer-api-external: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 5.271416ms
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 6.687957ms
      message: 'load-balancer-api-external: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 4.467613ms
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 7.863802ms
      message: 'load-balancer-api-external: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 4.016286ms
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 7.291618ms
      message: 'load-balancer-api-external: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 8.386585ms
      message: 'load-balancer-api-external: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 7.112571ms
      message: 'load-balancer-api-external: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "54234"
    uid: e614438d-9089-4b7a-bfe0-25725996fd0e
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:36:24Z"
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.495536ms
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 7.70396ms
      message: 'load-balancer-api-internal: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 4.260414ms
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 6.618037ms
      message: 'load-balancer-api-internal: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 4.428604ms
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 7.929123ms
      message: 'load-balancer-api-internal: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 4.047256ms
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 7.223086ms
      message: 'load-balancer-api-internal: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 6.108584ms
      message: 'load-balancer-api-internal: tcp connection to a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 7.137003ms
      message: 'load-balancer-api-internal: resolved host name a92c77600afb54e80a1b104a34b67b93-ce53dfa05cf4192c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-network-check-target-ip-10-0-130-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "53350"
    uid: f04ad99c-25a2-4c04-b1f0-74e47187baa5
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:37:24Z"
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.500707ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 2.696885ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 2.538635ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 2.55929ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 2.830639ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:24Z"
    - latency: 2.171697ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:24Z"
    - latency: 2.363057ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:24Z"
    - latency: 2.549193ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:24Z"
    - latency: 2.450804ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:24Z"
    - latency: 2.31962ms
      message: 'network-check-target-ip-10-0-130-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-network-check-target-ip-10-0-136-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "53351"
    uid: eebdfd38-da25-4cb8-befb-b6bce6296086
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:37:24Z"
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.440329ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 2.981022ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 2.675952ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 2.530528ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 2.760271ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:24Z"
    - latency: 2.384056ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:24Z"
    - latency: 2.484489ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:24Z"
    - latency: 2.625509ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:24Z"
    - latency: 2.269668ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:24Z"
    - latency: 2.40177ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-network-check-target-ip-10-0-141-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "53349"
    uid: 9154f46a-4b79-4c9f-b453-b769082fb0f7
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:37:24Z"
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.218µs
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 1.399545ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 2.186775ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 1.714661ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 1.332705ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:24Z"
    - latency: 1.062065ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:24Z"
    - latency: 1.028239ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:24Z"
    - latency: 937.195µs
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:24Z"
    - latency: 1.008585ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:24Z"
    - latency: 1.278723ms
      message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:30:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-75-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-75.ec2.internal
      uid: 95fb34f4-fae6-46b4-bf71-56e9667aa037
    resourceVersion: "54232"
    uid: 77fcbe91-4343-489d-80a7-dea43da5b3a7
  spec:
    sourcePod: network-check-source-989f8b8dc-qjzjz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:36:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 774.393µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 1.956882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:06:24Z"
    - latency: 891.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 1.820667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:05:24Z"
    - latency: 1.32023ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 2.617181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:24Z"
    - latency: 1.273441ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 2.143041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:24Z"
    - latency: 939.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:24Z"
    - latency: 2.145937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:24Z"
kind: List
metadata:
  resourceVersion: ""