apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "60517"
    uid: 89a1bc7b-c041-4578-9631-572c78f0073d
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:43:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 1.160013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 5.089316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 1.173708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 1.116101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:36Z"
    - latency: 1.154562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:36Z"
    - latency: 1.257374ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:36Z"
    - latency: 859.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:36Z"
    - latency: 1.187962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:36Z"
    - latency: 1.410471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "61369"
    uid: 2a22ef1b-9761-4213-8aee-fb2b6d0cb4ea
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:42:36Z"
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.196615ms
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 9.924897ms
      message: 'load-balancer-api-external: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 6.196937ms
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 9.206152ms
      message: 'load-balancer-api-external: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 4.119789ms
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 10.100358ms
      message: 'load-balancer-api-external: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 5.432006ms
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 11.273929ms
      message: 'load-balancer-api-external: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 3.642319ms
      message: 'load-balancer-api-external: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 7.687652ms
      message: 'load-balancer-api-external: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "61368"
    uid: f5f2e550-1a54-4fde-8e8c-97fa7883c2b3
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:42:36Z"
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.210057ms
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 10.001345ms
      message: 'load-balancer-api-internal: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 6.242603ms
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 9.185092ms
      message: 'load-balancer-api-internal: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 5.491598ms
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 10.052331ms
      message: 'load-balancer-api-internal: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 5.400169ms
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 10.765585ms
      message: 'load-balancer-api-internal: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 4.571066ms
      message: 'load-balancer-api-internal: tcp connection to a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 7.607325ms
      message: 'load-balancer-api-internal: resolved host name a4e99f8ad88104dfaa505e9fa64e7de3-0fea00203663a2d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-135-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "60515"
    uid: 78cfbfa1-283e-4e5b-9286-5c346a1043ea
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:43:36Z"
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.138246ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 2.252829ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 2.187153ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 2.326436ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 2.228309ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:36Z"
    - latency: 2.068454ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:36Z"
    - latency: 2.76596ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:36Z"
    - latency: 2.111999ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:36Z"
    - latency: 1.925148ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:36Z"
    - latency: 2.036004ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-137-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "60514"
    uid: d951eb5e-650e-4921-86e6-50fc3d5318d9
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:43:36Z"
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113664ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 1.88804ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 5.307531ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 1.27075ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 942.169µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:36Z"
    - latency: 1.240087ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:36Z"
    - latency: 1.4863ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:36Z"
    - latency: 1.255602ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:36Z"
    - latency: 1.212096ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:36Z"
    - latency: 1.138394ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-140-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "60516"
    uid: b8f930ef-7177-4e71-8303-563c526f3942
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:43:36Z"
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.612041ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 2.499374ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 5.4221ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 2.726311ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 2.48235ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:07:36Z"
    - latency: 2.365651ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:06:36Z"
    - latency: 2.214252ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:36Z"
    - latency: 2.111078ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:36Z"
    - latency: 2.686609ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:36Z"
    - latency: 2.634052ms
      message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: dc2137c8-316c-4cb7-b9be-954a552272bd
    resourceVersion: "61366"
    uid: bdbc1ac6-1a39-482e-800b-8cbcef5099a8
  spec:
    sourcePod: network-check-source-685456655f-gh899
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:42:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.298µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 1.942703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:36Z"
    - latency: 1.16142ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 2.38268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:36Z"
    - latency: 884.425µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 1.920661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:36Z"
    - latency: 1.099921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 6.009728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:09:36Z"
    - latency: 1.147397ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:36Z"
    - latency: 1.747614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:08:36Z"
kind: List
metadata:
  resourceVersion: ""