apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "69150"
    uid: ea445c08-2e99-44de-b4a1-f322f93e25f6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:28:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.125905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:29Z"
    - latency: 1.135498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 1.153135ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 1.034202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 1.026348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 860.958µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 956.202µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:04:29Z"
    - latency: 1.250556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:03:29Z"
    - latency: 854.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:02:29Z"
    - latency: 1.088652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "68074"
    uid: c2891dd9-00fd-49df-be79-d912121748e1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:27:29Z"
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.211765ms
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 7.26852ms
      message: 'load-balancer-api-external: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 5.185835ms
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 8.592545ms
      message: 'load-balancer-api-external: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 5.643277ms
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 6.998025ms
      message: 'load-balancer-api-external: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 6.608088ms
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 7.264722ms
      message: 'load-balancer-api-external: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 5.726077ms
      message: 'load-balancer-api-external: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 13.164168ms
      message: 'load-balancer-api-external: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:05:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "68075"
    uid: e169fdc8-fbab-47ee-9699-0c1fcedb90c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:27:29Z"
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.043559ms
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 7.361503ms
      message: 'load-balancer-api-internal: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 5.212059ms
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 8.575751ms
      message: 'load-balancer-api-internal: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 5.610062ms
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 7.018181ms
      message: 'load-balancer-api-internal: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 6.62136ms
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 7.161588ms
      message: 'load-balancer-api-internal: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 6.222811ms
      message: 'load-balancer-api-internal: tcp connection to a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 13.112565ms
      message: 'load-balancer-api-internal: resolved host name a152ca601a1b44b99bf6feebaebf6509-6a2671be78ca2423.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:05:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-128-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "69149"
    uid: 8918355f-bc70-4954-9af5-066607d6a4a4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:28:29Z"
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289618ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:29Z"
    - latency: 2.123444ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 2.070439ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 2.097228ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 2.119927ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 1.897138ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 1.982776ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:04:29Z"
    - latency: 2.263392ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:03:29Z"
    - latency: 1.979698ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:02:29Z"
    - latency: 2.099898ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-131-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "69147"
    uid: 5cdb411d-cd8f-4f29-a92c-a48dba875303
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:28:29Z"
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.479µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:29Z"
    - latency: 1.559659ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 919.911µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 1.162129ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 833.05µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 996.982µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 995.998µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:04:29Z"
    - latency: 1.442649ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:03:29Z"
    - latency: 1.057448ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:02:29Z"
    - latency: 959.62µs
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-135-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "69148"
    uid: 0bfd3f72-0758-4a20-915a-dd51f4acb9b1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:28:29Z"
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454916ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:10:29Z"
    - latency: 2.36722ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 2.54682ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 2.216438ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 2.42162ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 2.197539ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 2.071058ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:04:29Z"
    - latency: 1.828508ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:03:29Z"
    - latency: 2.268936ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:02:29Z"
    - latency: 2.350739ms
      message: 'network-check-target-ip-10-0-135-220: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:21:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-188.ec2.internal
      uid: 32771a9d-e9ba-4aec-808f-fad6fd9eb539
    resourceVersion: "68072"
    uid: 563da2af-cda2-42e9-b928-24900467ff32
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jt7ll
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:27:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.724µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 1.807602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:09:29Z"
    - latency: 859.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 1.866384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:08:29Z"
    - latency: 869.312µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 1.521505ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:07:29Z"
    - latency: 6.958945ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 2.078682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:06:29Z"
    - latency: 1.202318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:05:29Z"
    - latency: 1.681101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:05:29Z"
kind: List
metadata:
  resourceVersion: ""