apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "68693"
    uid: a7ad5a87-3a21-4c9f-900f-3942d5ccf30c
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:33:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:22:02Z"
    - latency: 1.179528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:21:02Z"
    - latency: 1.2572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 1.098013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 1.341675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 1.188203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 1.056607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 989.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:15:02Z"
    - latency: 1.153874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:14:02Z"
    - latency: 1.212529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "67026"
    uid: 10e0090b-d7e8-4cca-aff2-ae64cafee638
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:32:02Z"
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.793187ms
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 6.856579ms
      message: 'load-balancer-api-external: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 5.229508ms
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 7.290869ms
      message: 'load-balancer-api-external: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 4.993135ms
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 7.999899ms
      message: 'load-balancer-api-external: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 6.136942ms
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 7.54204ms
      message: 'load-balancer-api-external: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 5.631892ms
      message: 'load-balancer-api-external: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 6.370953ms
      message: 'load-balancer-api-external: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:16:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "67025"
    uid: 15d43a1c-f7e9-48c0-bb67-ad59bb99e091
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:32:02Z"
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.273808ms
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 6.806577ms
      message: 'load-balancer-api-internal: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 5.360544ms
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 7.210893ms
      message: 'load-balancer-api-internal: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 4.942894ms
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 8.072537ms
      message: 'load-balancer-api-internal: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 3.628339ms
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 7.513372ms
      message: 'load-balancer-api-internal: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 5.666712ms
      message: 'load-balancer-api-internal: tcp connection to a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 6.343262ms
      message: 'load-balancer-api-internal: resolved host name a6304631bcc4e4228abfbfaa291028fd-839704c9582eb2ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:16:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-131-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "68691"
    uid: 8cb1bbdf-dcd7-4786-a475-e7362d46c720
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:33:02Z"
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.602884ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:22:02Z"
    - latency: 2.59096ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:21:02Z"
    - latency: 2.514411ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 2.468928ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 2.532568ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 2.433606ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 2.481726ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 2.053083ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:15:02Z"
    - latency: 2.486199ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:14:02Z"
    - latency: 2.646597ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-134-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "68690"
    uid: 885176fc-78f4-4902-b959-abeaed7fb405
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:33:02Z"
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062999ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:22:02Z"
    - latency: 1.342136ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:21:02Z"
    - latency: 1.05396ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 1.469582ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 877.357µs
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 1.005899ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 1.455186ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 1.061875ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:15:02Z"
    - latency: 1.02073ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:14:02Z"
    - latency: 936.563µs
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-138-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "68692"
    uid: e2aed983-81ab-4b99-a1c9-0a07840f1554
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:33:02Z"
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.592266ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:22:02Z"
    - latency: 2.44292ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:21:02Z"
    - latency: 2.40122ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 2.600223ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 2.394766ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 2.608948ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 2.199156ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 2.70036ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:15:02Z"
    - latency: 2.534234ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:14:02Z"
    - latency: 2.67783ms
      message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:26:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.ec2.internal
      uid: f77136e9-4f1f-4f74-8fe2-6f796c349ab0
    resourceVersion: "67024"
    uid: 77b1c338-8084-4cfb-aaee-f7c7f6160783
  spec:
    sourcePod: network-check-source-65bdbbff45-6fqhl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:32:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039901ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 2.333634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:20:02Z"
    - latency: 902.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 1.929165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:19:02Z"
    - latency: 1.094493ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 1.860458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:18:02Z"
    - latency: 932.932µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 1.861498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:17:02Z"
    - latency: 1.201155ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:16:02Z"
    - latency: 1.771139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:16:02Z"
kind: List
metadata:
  resourceVersion: ""