apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "19525"
    uid: ab6a51d9-bcfc-4df5-bffd-d978eb0b8ee1
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:44:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.814µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 1.492063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 1.900272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:39Z"
    - latency: 911.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:39Z"
    - latency: 707.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:39Z"
    - latency: 830.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:39Z"
    - latency: 1.006596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:52:39Z"
    - latency: 1.746937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:51:39Z"
    - latency: 980.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:50:39Z"
    - latency: 1.011733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "20725"
    uid: 9e08e354-839e-4704-b25c-dbc5e31a239b
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:43:39Z"
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.170316ms
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 10.429286ms
      message: 'load-balancer-api-external: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 7.406208ms
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 12.178156ms
      message: 'load-balancer-api-external: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 5.515647ms
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 8.573461ms
      message: 'load-balancer-api-external: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 6.138755ms
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 8.000572ms
      message: 'load-balancer-api-external: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 5.430081ms
      message: 'load-balancer-api-external: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 7.846454ms
      message: 'load-balancer-api-external: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "20726"
    uid: e569a6a3-246f-4d69-80d1-4013d2cf46fd
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:43:39Z"
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.113929ms
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 10.459132ms
      message: 'load-balancer-api-internal: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 5.660564ms
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 11.814619ms
      message: 'load-balancer-api-internal: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 5.530348ms
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 8.636533ms
      message: 'load-balancer-api-internal: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 6.129459ms
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 7.951908ms
      message: 'load-balancer-api-internal: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 5.467791ms
      message: 'load-balancer-api-internal: tcp connection to a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 7.800384ms
      message: 'load-balancer-api-internal: resolved host name a7a416c1874a945f5a17bee27b8a73e5-8c8b7210b433275e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-137-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "19523"
    uid: 08a663c5-0c9f-4887-bdcb-be2665d8e150
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:44:39Z"
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.396126ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 2.651112ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 2.642374ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:39Z"
    - latency: 1.912108ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:39Z"
    - latency: 2.250586ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:39Z"
    - latency: 2.269278ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:39Z"
    - latency: 2.434952ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:52:39Z"
    - latency: 2.589915ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:51:39Z"
    - latency: 2.132581ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:50:39Z"
    - latency: 2.454383ms
      message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-142-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "19524"
    uid: 4d5c127b-9e1e-429f-9911-0357bec79bf6
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:44:39Z"
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.27274ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 2.140824ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 2.49945ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:39Z"
    - latency: 1.828073ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:39Z"
    - latency: 2.375696ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:39Z"
    - latency: 2.116499ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:39Z"
    - latency: 2.338597ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:52:39Z"
    - latency: 2.539975ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:51:39Z"
    - latency: 2.402343ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:50:39Z"
    - latency: 2.410363ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-143-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "19522"
    uid: 2bb05107-05d0-4138-a4a6-a813b7c036c7
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:44:39Z"
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.702µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 792.223µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 1.134501ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:39Z"
    - latency: 955.013µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:39Z"
    - latency: 1.271314ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:39Z"
    - latency: 947.242µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:39Z"
    - latency: 925.197µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:52:39Z"
    - latency: 792.676µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:51:39Z"
    - latency: 1.042312ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:50:39Z"
    - latency: 876.527µs
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-186.ec2.internal
      uid: 006c44f4-0ffb-488b-b482-0866fb713e54
    resourceVersion: "20724"
    uid: 59a5c503-fbcb-4ca4-b41b-0ac8d278af72
  spec:
    sourcePod: network-check-source-685456655f-ft2gk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:43:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 1.672981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:39Z"
    - latency: 794.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 3.900742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:39Z"
    - latency: 1.487388ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 1.707011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:59:39Z"
    - latency: 826.581µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 1.588352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:58:39Z"
    - latency: 959.424µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:39Z"
    - latency: 1.630831ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:57:39Z"
kind: List
metadata:
  resourceVersion: ""