apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "60073"
    uid: 9977d49f-8658-4dde-981b-aaa43aab42db
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:50:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.526578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 1.098796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 1.540647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 1.032849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:08:17Z"
    - latency: 1.775448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:17Z"
    - latency: 1.103659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:17Z"
    - latency: 1.401515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:17Z"
    - latency: 1.095901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:17Z"
    - latency: 1.034051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:17Z"
    - latency: 1.225736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "61579"
    uid: de803b2d-1600-4f98-a836-8e430d6d37e9
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:49:17Z"
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.6297ms
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 7.997564ms
      message: 'load-balancer-api-external: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 4.220206ms
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 9.44703ms
      message: 'load-balancer-api-external: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 5.92507ms
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 6.899127ms
      message: 'load-balancer-api-external: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 5.241717ms
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 8.893487ms
      message: 'load-balancer-api-external: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 5.731245ms
      message: 'load-balancer-api-external: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 7.638538ms
      message: 'load-balancer-api-external: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:09:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "61580"
    uid: de40f89d-eb2c-41e6-a96e-fad64a0cf0de
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:49:17Z"
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.43618ms
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 7.934273ms
      message: 'load-balancer-api-internal: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 4.193307ms
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 9.405698ms
      message: 'load-balancer-api-internal: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 6.133286ms
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 6.861815ms
      message: 'load-balancer-api-internal: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 5.302364ms
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 8.826031ms
      message: 'load-balancer-api-internal: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 5.712387ms
      message: 'load-balancer-api-internal: tcp connection to ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 7.613063ms
      message: 'load-balancer-api-internal: resolved host name ad6fc0cc0dfed4f898cf759207a72cb0-4b00f2fb703a22a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:09:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-132-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "60072"
    uid: 83729623-f995-4c79-a41a-329ad5c4325f
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:50:17Z"
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.478323ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 2.553697ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 2.343983ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 2.443209ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:08:17Z"
    - latency: 3.0719ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:17Z"
    - latency: 2.514892ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:17Z"
    - latency: 2.541361ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:17Z"
    - latency: 2.759601ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:17Z"
    - latency: 3.2853ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:17Z"
    - latency: 3.075813ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-139-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "60070"
    uid: 6d954296-ab10-4bfd-bd91-a917e0b34f25
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:50:17Z"
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.373313ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 1.360134ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 893.031µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 1.03314ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:08:17Z"
    - latency: 912.002µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:17Z"
    - latency: 1.909813ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:17Z"
    - latency: 967.758µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:17Z"
    - latency: 1.72741ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:17Z"
    - latency: 1.611256ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:17Z"
    - latency: 868.923µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-140-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "60071"
    uid: 294096c6-bd40-494e-8757-7e9ffb139699
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:50:17Z"
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.134235ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 2.799606ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 2.401213ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 2.477636ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:08:17Z"
    - latency: 2.338299ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:17Z"
    - latency: 2.525875ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:17Z"
    - latency: 2.413709ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:17Z"
    - latency: 2.693817ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:17Z"
    - latency: 2.394198ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:17Z"
    - latency: 2.338636ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T16:43:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e60aa763-e91b-4f0e-a7e6-806798b7f43a
    resourceVersion: "61578"
    uid: daffa40e-5a3f-4932-9e4a-c5dc49c673b6
  spec:
    sourcePod: network-check-source-6f8b768455-bcr92
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:49:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.678µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 1.808121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:13:17Z"
    - latency: 1.246282ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 1.765305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:12:17Z"
    - latency: 1.454979ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 1.940794ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:11:17Z"
    - latency: 1.194845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 1.994567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:10:17Z"
    - latency: 919.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:09:17Z"
    - latency: 2.074381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:09:17Z"
kind: List
metadata:
  resourceVersion: ""