apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "70594"
    uid: 4054a139-14c8-4086-a442-b4f4541f285a
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:17:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.593µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:06:28Z"
    - latency: 1.196718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:05:28Z"
    - latency: 1.271891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 1.213203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 1.452077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 1.250701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 1.014315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 1.311343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:59:28Z"
    - latency: 1.074402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:58:28Z"
    - latency: 977.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "68232"
    uid: 910ef734-0d95-41f9-9afb-48b9182dce91
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:16:28Z"
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.991347ms
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 9.645567ms
      message: 'load-balancer-api-external: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 7.351428ms
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 8.489024ms
      message: 'load-balancer-api-external: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 4.139774ms
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 9.828263ms
      message: 'load-balancer-api-external: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 4.441512ms
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 8.95786ms
      message: 'load-balancer-api-external: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 5.941768ms
      message: 'load-balancer-api-external: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 9.542596ms
      message: 'load-balancer-api-external: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "68231"
    uid: 1258d1fc-f3a6-4edb-8913-aeb7ae8a9bff
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:16:28Z"
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.727757ms
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 9.702666ms
      message: 'load-balancer-api-internal: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 6.935617ms
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 8.641006ms
      message: 'load-balancer-api-internal: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 4.040774ms
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 9.624681ms
      message: 'load-balancer-api-internal: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 3.374529ms
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 9.029893ms
      message: 'load-balancer-api-internal: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 4.171876ms
      message: 'load-balancer-api-internal: tcp connection to abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 9.334516ms
      message: 'load-balancer-api-internal: resolved host name abc1f6965c8d64e8bb1a86cc687799cf-7f916782a3580071.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-128-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "70592"
    uid: 0623a3b0-af92-48b5-acad-c24686814fed
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:17:28Z"
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177665ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:06:28Z"
    - latency: 2.204918ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:05:28Z"
    - latency: 1.957176ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 2.651431ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 2.726565ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 2.327534ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 2.521841ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 2.357984ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:59:28Z"
    - latency: 2.382776ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:58:28Z"
    - latency: 2.366813ms
      message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "70591"
    uid: d9554faa-1854-45df-a788-3da68bc61f22
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:17:28Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.9µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:06:28Z"
    - latency: 1.001599ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:05:28Z"
    - latency: 1.197711ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 1.217784ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 2.258307ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 903.098µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 1.005209ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 891.445µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:59:28Z"
    - latency: 856.085µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:58:28Z"
    - latency: 961.8µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-139-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "70593"
    uid: 444cb02c-b5d9-4bcc-8af0-27f7cc918829
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:17:28Z"
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.096832ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:06:28Z"
    - latency: 2.143019ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:05:28Z"
    - latency: 1.922623ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 2.270642ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 2.304775ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 2.20988ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 2.030403ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 2.127653ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:59:28Z"
    - latency: 1.821498ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:58:28Z"
    - latency: 1.710541ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:10:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: 9b58e351-ed3e-4bd0-bd4e-580c37bf06ab
    resourceVersion: "68230"
    uid: 9f0d916e-f927-43cd-beed-fab79be6558c
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk75t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:16:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 1.736474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:04:28Z"
    - latency: 864.821µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 2.191734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:03:28Z"
    - latency: 847.236µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 2.578285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:02:28Z"
    - latency: 1.17252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 1.822787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:01:28Z"
    - latency: 777.22µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T20:00:28Z"
    - latency: 2.547473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T20:00:28Z"
kind: List
metadata:
  resourceVersion: ""