apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "60153"
    uid: 76ad8345-288a-48ce-9d69-d1ca3536154b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:20:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:55:33Z"
    - latency: 915.26µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:54:33Z"
    - latency: 872.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:53:33Z"
    - latency: 961.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:52:33Z"
    - latency: 949.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:51:33Z"
    - latency: 1.006863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:50:33Z"
    - latency: 1.409778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:49:33Z"
    - latency: 1.374241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:48:33Z"
    - latency: 1.180204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:47:33Z"
    - latency: 989.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "65872"
    uid: 83b7142b-f8a7-4145-9009-6a337dcd56ab
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:19:34Z"
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.283102ms
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 9.103013ms
      message: 'load-balancer-api-external: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 4.592564ms
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 7.341475ms
      message: 'load-balancer-api-external: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 4.917819ms
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 7.133449ms
      message: 'load-balancer-api-external: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 5.09205ms
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 7.744473ms
      message: 'load-balancer-api-external: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 5.076372ms
      message: 'load-balancer-api-external: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:57:33Z"
    - latency: 12.512544ms
      message: 'load-balancer-api-external: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:57:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "65871"
    uid: 2e0d1f4a-68d0-467c-9c3a-0c4366db8dc9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:19:34Z"
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.231818ms
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 9.15403ms
      message: 'load-balancer-api-internal: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 5.120393ms
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 7.375ms
      message: 'load-balancer-api-internal: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 6.191268ms
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 7.154589ms
      message: 'load-balancer-api-internal: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 5.809068ms
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 7.795437ms
      message: 'load-balancer-api-internal: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 5.090746ms
      message: 'load-balancer-api-internal: tcp connection to a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:57:33Z"
    - latency: 12.540794ms
      message: 'load-balancer-api-internal: resolved host name a77960177285e452e81753920abeede6-6281169f59a0d920.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:57:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-network-check-target-ip-10-0-128-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "60150"
    uid: 48513424-e799-4de1-aa85-031d44e6bd89
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:20:33Z"
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446092ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:55:33Z"
    - latency: 2.22901ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:54:33Z"
    - latency: 2.156054ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:53:33Z"
    - latency: 1.977719ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:52:33Z"
    - latency: 2.229499ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:51:33Z"
    - latency: 2.082958ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:50:33Z"
    - latency: 2.867577ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:49:33Z"
    - latency: 2.256673ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:48:33Z"
    - latency: 2.476863ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:47:33Z"
    - latency: 2.291799ms
      message: 'network-check-target-ip-10-0-128-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-network-check-target-ip-10-0-138-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "60151"
    uid: ff863c7c-c716-4075-a265-78bf18efeef8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:20:33Z"
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.473455ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:55:33Z"
    - latency: 2.377057ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:54:33Z"
    - latency: 2.079065ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:53:33Z"
    - latency: 2.118647ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:52:33Z"
    - latency: 2.212221ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:51:33Z"
    - latency: 2.16189ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:50:33Z"
    - latency: 2.138079ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:49:33Z"
    - latency: 2.294263ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:48:33Z"
    - latency: 2.332901ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:47:33Z"
    - latency: 2.10226ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-network-check-target-ip-10-0-140-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "60149"
    uid: 4b67f6b8-19af-4d70-a883-5d93cfd1e1f3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:20:33Z"
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.59966ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:55:33Z"
    - latency: 863.035µs
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:54:33Z"
    - latency: 1.357814ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:53:33Z"
    - latency: 881.737µs
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:52:33Z"
    - latency: 1.007131ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:51:33Z"
    - latency: 1.234676ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:50:33Z"
    - latency: 1.436356ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:49:33Z"
    - latency: 910.149µs
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:48:33Z"
    - latency: 1.660056ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:47:33Z"
    - latency: 1.373912ms
      message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T15:13:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-166.ec2.internal
      uid: c2fa1565-e06b-4bd8-825a-49cf83f279f1
    resourceVersion: "65870"
    uid: 1b429c7a-f47f-467c-956e-a706f6fcf07e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfg4f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:19:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054618ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 1.940856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:01:33Z"
    - latency: 888.645µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 1.69722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T16:00:33Z"
    - latency: 1.009826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 1.818305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:59:33Z"
    - latency: 871.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 1.706654ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:58:33Z"
    - latency: 1.235321ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:57:33Z"
    - latency: 1.766518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:57:33Z"
kind: List
metadata:
  resourceVersion: ""