apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "51286"
    uid: 94a3b0f1-fc71-4056-9be0-32cb44393adb
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:03:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.066706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:24:22Z"
    - latency: 804.839µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:23:22Z"
    - latency: 1.188445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:22:22Z"
    - latency: 1.219264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:21:22Z"
    - latency: 1.000026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 945.153µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 988.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 1.193676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 967.142µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 1.274686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "47844"
    uid: dba2077a-5e82-4edc-a3ab-dd0011621cac
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:02:22Z"
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.532422ms
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 6.278902ms
      message: 'load-balancer-api-external: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 4.445908ms
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 7.447103ms
      message: 'load-balancer-api-external: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 3.080986ms
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 8.654841ms
      message: 'load-balancer-api-external: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 6.127283ms
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 7.031892ms
      message: 'load-balancer-api-external: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 3.994347ms
      message: 'load-balancer-api-external: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 7.900535ms
      message: 'load-balancer-api-external: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:16:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "47843"
    uid: ffebbeaf-99d5-42e7-89eb-70812bc20ff8
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:02:22Z"
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.496691ms
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 6.320832ms
      message: 'load-balancer-api-internal: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 4.297748ms
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 7.364858ms
      message: 'load-balancer-api-internal: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 3.88511ms
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 8.715684ms
      message: 'load-balancer-api-internal: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 4.046104ms
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 6.959164ms
      message: 'load-balancer-api-internal: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 4.01256ms
      message: 'load-balancer-api-internal: tcp connection to a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 7.807888ms
      message: 'load-balancer-api-internal: resolved host name a3bf3c75a71fe4c4a8827b9cd2c06c9c-055c59c030f58aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:16:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-128-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "51283"
    uid: ca5a1fb1-a321-4a6e-ac04-6e753e552c7d
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:03:22Z"
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.650803ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:24:22Z"
    - latency: 746.21µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:23:22Z"
    - latency: 958.11µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:22:22Z"
    - latency: 1.192943ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:21:22Z"
    - latency: 874.211µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 1.099743ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 1.075649ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 1.004252ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 1.046131ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 939.078µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-133-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "51284"
    uid: d51e5607-62c7-466a-90a6-2150b2bc073a
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:03:22Z"
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.026964ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:24:22Z"
    - latency: 1.981339ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:23:22Z"
    - latency: 1.906217ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:22:22Z"
    - latency: 1.923799ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:21:22Z"
    - latency: 1.606156ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 1.825391ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 2.103336ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 2.167161ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 1.79738ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 1.889921ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-134-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "51285"
    uid: bc638c09-68f3-47a0-b9f5-8c16043d1e19
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:03:22Z"
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260513ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:24:22Z"
    - latency: 2.319159ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:23:22Z"
    - latency: 2.353364ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:22:22Z"
    - latency: 2.187706ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:21:22Z"
    - latency: 2.119943ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 2.238222ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 2.408288ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 2.736883ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 2.319874ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 2.201127ms
      message: 'network-check-target-ip-10-0-134-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T21:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: b45e1015-61ba-4518-9265-5332800ad00b
    resourceVersion: "47842"
    uid: 8c764df0-7f9c-4661-98f7-0a0259b94f02
  spec:
    sourcePod: network-check-source-685456655f-vbzm9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:02:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026177ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 1.75751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:20:22Z"
    - latency: 867.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 1.719442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:19:22Z"
    - latency: 1.356839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 1.933425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:18:22Z"
    - latency: 973.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 1.759317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:17:22Z"
    - latency: 972.767µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:16:22Z"
    - latency: 2.150387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:16:22Z"
kind: List
metadata:
  resourceVersion: ""