apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "54631"
    uid: 39dcc1eb-9e09-4692-9c44-ef207e953144
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:08:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.123856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 1.082845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 1.059283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 1.125572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:26:39Z"
    - latency: 779.826µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:25:39Z"
    - latency: 1.013306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:24:39Z"
    - latency: 1.122564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:23:39Z"
    - latency: 1.152382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:22:39Z"
    - latency: 1.372996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:21:39Z"
    - latency: 1.37124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "56341"
    uid: 8543b85a-37c9-4715-9eae-9334f2ba2d7b
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:07:39Z"
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.34177ms
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 8.177023ms
      message: 'load-balancer-api-external: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 5.158162ms
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 7.987949ms
      message: 'load-balancer-api-external: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 3.90506ms
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 8.046155ms
      message: 'load-balancer-api-external: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 5.087334ms
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 8.242928ms
      message: 'load-balancer-api-external: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 3.856605ms
      message: 'load-balancer-api-external: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 7.828252ms
      message: 'load-balancer-api-external: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:27:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "56340"
    uid: 6e824646-de53-4bcb-bc28-f1c74eaa4ded
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:07:39Z"
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.303971ms
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 8.250879ms
      message: 'load-balancer-api-internal: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 5.131058ms
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 8.069859ms
      message: 'load-balancer-api-internal: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 3.92212ms
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 8.027916ms
      message: 'load-balancer-api-internal: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 5.337764ms
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 8.154611ms
      message: 'load-balancer-api-internal: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 4.847001ms
      message: 'load-balancer-api-internal: tcp connection to a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 7.882771ms
      message: 'load-balancer-api-internal: resolved host name a6cfca3a124264c8daedaf38b3f91243-a3161b577105e02c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:27:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-128-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "54628"
    uid: f8e7994a-2438-4e42-bc3d-2f1790b7115d
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:08:39Z"
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.69µs
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 996.705µs
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 1.461685ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 1.348706ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:26:39Z"
    - latency: 1.029567ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:25:39Z"
    - latency: 1.518516ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:24:39Z"
    - latency: 1.006921ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:23:39Z"
    - latency: 948.231µs
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:22:39Z"
    - latency: 1.385897ms
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:21:39Z"
    - latency: 906.729µs
      message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-130-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "54629"
    uid: d3339f90-7962-43f8-99df-502fbca3c2c9
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:08:39Z"
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.696943ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 1.845788ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 1.781241ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 1.725363ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:26:39Z"
    - latency: 1.985576ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:25:39Z"
    - latency: 2.06376ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:24:39Z"
    - latency: 1.936851ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:23:39Z"
    - latency: 2.286808ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:22:39Z"
    - latency: 1.995141ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:21:39Z"
    - latency: 1.776379ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-134-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "54630"
    uid: 9d751bce-cbcc-48a1-a28e-85306f63b4c0
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:08:39Z"
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.310042ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 1.85091ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 2.157904ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 2.337363ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:26:39Z"
    - latency: 2.040213ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:25:39Z"
    - latency: 2.380645ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:24:39Z"
    - latency: 2.370116ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:23:39Z"
    - latency: 2.270566ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:22:39Z"
    - latency: 2.319105ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:21:39Z"
    - latency: 2.287622ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T05:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-168-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-168.ec2.internal
      uid: ba9136c8-e425-45bd-b62f-cda3966a998d
    resourceVersion: "56338"
    uid: 29967f34-09c8-4915-b950-c1204c9b55dc
  spec:
    sourcePod: network-check-source-685456655f-gkf6c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T05:07:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 807.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 1.655953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:31:39Z"
    - latency: 824.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 1.817716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:30:39Z"
    - latency: 1.156756ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 1.638376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:29:39Z"
    - latency: 978.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 1.749855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:28:39Z"
    - latency: 1.449275ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T05:27:39Z"
    - latency: 1.626183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T05:27:39Z"
kind: List
metadata:
  resourceVersion: ""