apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "53818"
    uid: 35eb25ab-2fb5-4ce7-990c-40005b00852f
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:01:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.345399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 1.388107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 1.280982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 1.03807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:19:30Z"
    - latency: 1.650415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:18:30Z"
    - latency: 1.030763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:17:30Z"
    - latency: 1.138713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:16:30Z"
    - latency: 1.975808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:15:30Z"
    - latency: 925.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:14:30Z"
    - latency: 1.232823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "55652"
    uid: 97ca1a98-9375-40eb-88e7-460341f67e7a
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:00:30Z"
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.926227ms
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 7.276743ms
      message: 'load-balancer-api-external: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 5.818059ms
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 6.432536ms
      message: 'load-balancer-api-external: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 4.371791ms
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 6.330894ms
      message: 'load-balancer-api-external: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 4.074946ms
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 7.929671ms
      message: 'load-balancer-api-external: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 5.356245ms
      message: 'load-balancer-api-external: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 10.181368ms
      message: 'load-balancer-api-external: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "55651"
    uid: f2538b31-f0be-45bd-8f18-95ed5455de4f
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:00:30Z"
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.928718ms
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 7.221973ms
      message: 'load-balancer-api-internal: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 5.808035ms
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 6.48036ms
      message: 'load-balancer-api-internal: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 3.895683ms
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 6.366501ms
      message: 'load-balancer-api-internal: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 4.678745ms
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 7.950489ms
      message: 'load-balancer-api-internal: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 5.307609ms
      message: 'load-balancer-api-internal: tcp connection to a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 10.238694ms
      message: 'load-balancer-api-internal: resolved host name a24d528c71b2d4342a26a9655edba430-10a2c98785d4df73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-network-check-target-ip-10-0-128-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "53815"
    uid: 4f0b4680-3254-4eab-943f-0ed5d97dda30
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:01:30Z"
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068793ms
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 986.84µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 837.422µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 1.001426ms
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:19:30Z"
    - latency: 980.831µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:18:30Z"
    - latency: 926.524µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:17:30Z"
    - latency: 976.865µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:16:30Z"
    - latency: 15.26786ms
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:15:30Z"
    - latency: 1.364244ms
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:14:30Z"
    - latency: 959.334µs
      message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-network-check-target-ip-10-0-132-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "53816"
    uid: 89ef29a3-1aea-478f-90d6-955a65bb3d85
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:01:30Z"
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.106108ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 1.970789ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 1.963859ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 1.978996ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:19:30Z"
    - latency: 2.074984ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:18:30Z"
    - latency: 2.0897ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:17:30Z"
    - latency: 2.354722ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:16:30Z"
    - latency: 10.289806ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:15:30Z"
    - latency: 2.115702ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:14:30Z"
    - latency: 1.758552ms
      message: 'network-check-target-ip-10-0-132-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-network-check-target-ip-10-0-142-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "53817"
    uid: 71732e3e-b903-4199-9e73-f6947693b904
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:01:30Z"
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.406906ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 2.279103ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 2.038116ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 2.167736ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:19:30Z"
    - latency: 2.393963ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:18:30Z"
    - latency: 2.393779ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:17:30Z"
    - latency: 2.356929ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:16:30Z"
    - latency: 10.496274ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:15:30Z"
    - latency: 2.076375ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:14:30Z"
    - latency: 2.319257ms
      message: 'network-check-target-ip-10-0-142-122: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:54:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-206-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-206.ec2.internal
      uid: e9b3328c-f0d5-4669-9aec-23e2e331b7b7
    resourceVersion: "55650"
    uid: ead858c7-003b-4428-b562-f3b0870388db
  spec:
    sourcePod: network-check-source-685456655f-l26h6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T07:00:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 1.775717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:24:30Z"
    - latency: 986.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 1.829237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:23:30Z"
    - latency: 1.060664ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 1.786694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:22:30Z"
    - latency: 957.792µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 2.259547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:21:30Z"
    - latency: 932.705µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:20:30Z"
    - latency: 1.924138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:20:30Z"
kind: List
metadata:
  resourceVersion: ""