apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "69723"
    uid: f19075ec-294e-45c2-bcca-194fbd08b2be
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.184131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 1.136256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:49:56Z"
    - latency: 1.214629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:48:56Z"
    - latency: 1.093116ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:47:56Z"
    - latency: 896.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:46:56Z"
    - latency: 830.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:45:56Z"
    - latency: 889.218µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:44:56Z"
    - latency: 1.236196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:43:56Z"
    - latency: 1.489548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:56Z"
    - latency: 918.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "74081"
    uid: f352362c-be1e-414f-a0c6-32766c0819d6
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:56Z"
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.346045ms
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 7.541498ms
      message: 'load-balancer-api-external: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 4.66028ms
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 7.088601ms
      message: 'load-balancer-api-external: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 4.454474ms
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 7.205971ms
      message: 'load-balancer-api-external: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 5.575658ms
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 7.0731ms
      message: 'load-balancer-api-external: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 5.383987ms
      message: 'load-balancer-api-external: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 7.16333ms
      message: 'load-balancer-api-external: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:50:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "74080"
    uid: 78eec776-02df-4cac-9e99-0b386df1ad04
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:56Z"
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.444703ms
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 7.445027ms
      message: 'load-balancer-api-internal: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 4.615547ms
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 7.102798ms
      message: 'load-balancer-api-internal: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 6.433351ms
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 7.237172ms
      message: 'load-balancer-api-internal: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 5.470422ms
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 7.058632ms
      message: 'load-balancer-api-internal: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 5.379257ms
      message: 'load-balancer-api-internal: tcp connection to a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 7.050986ms
      message: 'load-balancer-api-internal: resolved host name a2ee0083f4cf34d82b92ec18c8cbfa6f-322a17d1696c41c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:50:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-network-check-target-ip-10-0-131-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "69722"
    uid: f2300139-6c88-45b4-bf9d-6b57cf601717
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:56Z"
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.519658ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 2.174356ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:49:56Z"
    - latency: 2.451885ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:48:56Z"
    - latency: 2.821212ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:47:56Z"
    - latency: 2.400134ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:46:56Z"
    - latency: 2.189768ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:45:56Z"
    - latency: 2.235061ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:44:56Z"
    - latency: 2.335049ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:43:56Z"
    - latency: 2.26946ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:56Z"
    - latency: 2.266538ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-network-check-target-ip-10-0-134-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "69721"
    uid: 4dd7f4ed-fe7f-4839-97d5-c069e5c49d26
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:56Z"
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.194298ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 1.978572ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:49:56Z"
    - latency: 2.3164ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:48:56Z"
    - latency: 2.124213ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:47:56Z"
    - latency: 2.615058ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:46:56Z"
    - latency: 2.361576ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:45:56Z"
    - latency: 2.223134ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:44:56Z"
    - latency: 2.299492ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:43:56Z"
    - latency: 2.109048ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:56Z"
    - latency: 2.017768ms
      message: 'network-check-target-ip-10-0-134-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-network-check-target-ip-10-0-139-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "69720"
    uid: 1f5ef926-897a-4ccd-bcce-47fb9ad8fb19
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:56Z"
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.35µs
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 1.045169ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:49:56Z"
    - latency: 1.066641ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:48:56Z"
    - latency: 1.075895ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:47:56Z"
    - latency: 1.40312ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:46:56Z"
    - latency: 1.056189ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:45:56Z"
    - latency: 1.312423ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:44:56Z"
    - latency: 1.130278ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:43:56Z"
    - latency: 1.175743ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:56Z"
    - latency: 850.138µs
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-36.ec2.internal
      uid: 8f31450c-62d3-41e0-a101-8250e8631c7a
    resourceVersion: "74079"
    uid: f28503f9-c46e-401d-823a-5616dddc9fd5
  spec:
    sourcePod: network-check-source-7cbc45fddc-kdcrx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 2.080539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:54:56Z"
    - latency: 1.20512ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 1.806861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:53:56Z"
    - latency: 1.016323ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 1.928319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:52:56Z"
    - latency: 1.032002ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 2.49157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:51:56Z"
    - latency: 1.348847ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:50:56Z"
    - latency: 1.917363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:50:56Z"
kind: List
metadata:
  resourceVersion: ""