apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "54510"
    uid: db03c342-2ad4-42f3-9281-59d0d841ee62
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:13:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.199942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 991.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 1.111329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 1.064085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 1.000886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:37:50Z"
    - latency: 1.205196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:36:50Z"
    - latency: 882.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:35:50Z"
    - latency: 1.357892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:34:50Z"
    - latency: 1.371795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:33:50Z"
    - latency: 1.01152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:32:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "55531"
    uid: 35df5b54-6f15-47ef-9b27-d8c32963eceb
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:12:50Z"
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.183634ms
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 8.731302ms
      message: 'load-balancer-api-external: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 5.265226ms
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 9.173684ms
      message: 'load-balancer-api-external: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 5.088807ms
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 6.785053ms
      message: 'load-balancer-api-external: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 6.485267ms
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 8.890814ms
      message: 'load-balancer-api-external: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 4.779216ms
      message: 'load-balancer-api-external: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 7.374596ms
      message: 'load-balancer-api-external: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "55532"
    uid: fd314aae-b020-4a63-99fd-bb5773546915
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:12:50Z"
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.14355ms
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 8.741454ms
      message: 'load-balancer-api-internal: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 4.234264ms
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 9.266525ms
      message: 'load-balancer-api-internal: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 3.679656ms
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 6.809118ms
      message: 'load-balancer-api-internal: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 5.82131ms
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 8.991387ms
      message: 'load-balancer-api-internal: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 4.237138ms
      message: 'load-balancer-api-internal: tcp connection to aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 7.412679ms
      message: 'load-balancer-api-internal: resolved host name aac423baeea8f4530830a16482df5d94-08ed30da3a1b7012.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-network-check-target-ip-10-0-131-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "54509"
    uid: f4a17fe6-ff0f-4d64-b794-374ce7a55804
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:13:50Z"
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.48694ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 1.791024ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 1.866804ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 2.053953ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 1.879625ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:37:50Z"
    - latency: 2.116935ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:36:50Z"
    - latency: 2.071087ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:35:50Z"
    - latency: 1.895023ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:34:50Z"
    - latency: 1.898995ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:33:50Z"
    - latency: 2.13272ms
      message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:32:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-network-check-target-ip-10-0-134-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "54508"
    uid: 4aa631f1-ec1e-473d-9c62-adebfc055f3b
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:13:50Z"
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.539735ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 2.08596ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 2.31326ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 2.173762ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 2.096492ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:37:50Z"
    - latency: 2.323932ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:36:50Z"
    - latency: 2.165296ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:35:50Z"
    - latency: 2.341025ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:34:50Z"
    - latency: 2.527894ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:33:50Z"
    - latency: 2.095739ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:32:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-network-check-target-ip-10-0-139-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "54507"
    uid: 8f22463f-be3e-4365-853c-1178472118d2
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:13:50Z"
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.94µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 904.967µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 938.346µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 995.216µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 887.919µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:37:50Z"
    - latency: 933.514µs
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:36:50Z"
    - latency: 1.16633ms
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:35:50Z"
    - latency: 2.090401ms
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:34:50Z"
    - latency: 1.754047ms
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:33:50Z"
    - latency: 1.347642ms
      message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:32:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-213.ec2.internal
      uid: 78c7863c-7668-4e47-acce-d7be2ee7d2e3
    resourceVersion: "55530"
    uid: de54ce57-5d07-4214-b3a3-5d116f1328ed
  spec:
    sourcePod: network-check-source-989f8b8dc-qh56q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:12:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034256ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 1.837593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:42:50Z"
    - latency: 1.218914ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 1.70995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:41:50Z"
    - latency: 1.165183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 1.739918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:40:50Z"
    - latency: 1.348112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 1.814692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:39:50Z"
    - latency: 907.417µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:38:50Z"
    - latency: 2.332938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:38:50Z"
kind: List
metadata:
  resourceVersion: ""