apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61347"
    uid: 305b61e8-8fd3-4dbb-9bc6-84bc062b2857
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:31:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.851175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 1.50993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 1.186212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 1.071091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 1.085475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 1.26288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:01:29Z"
    - latency: 1.28216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:00:29Z"
    - latency: 1.277352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:59:29Z"
    - latency: 1.223071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:58:29Z"
    - latency: 1.122404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61348"
    uid: a8aa6f18-d8c0-4440-af1e-76ef09471149
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:30:29Z"
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.458031ms
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 7.324525ms
      message: 'load-balancer-api-external: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 6.087476ms
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 6.845492ms
      message: 'load-balancer-api-external: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 3.490057ms
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 6.500108ms
      message: 'load-balancer-api-external: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 4.167521ms
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 7.657437ms
      message: 'load-balancer-api-external: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 5.125865ms
      message: 'load-balancer-api-external: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 6.708442ms
      message: 'load-balancer-api-external: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61349"
    uid: e7826aa7-9fb4-4550-ba94-cd7f563a7d7f
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:30:29Z"
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.461613ms
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 7.207738ms
      message: 'load-balancer-api-internal: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 5.954162ms
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 6.792376ms
      message: 'load-balancer-api-internal: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 3.031229ms
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 6.447162ms
      message: 'load-balancer-api-internal: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 4.138866ms
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 7.701813ms
      message: 'load-balancer-api-internal: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 5.133906ms
      message: 'load-balancer-api-internal: tcp connection to ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 6.640111ms
      message: 'load-balancer-api-internal: resolved host name ae8d2bf9325d047709327e622ec6b259-210acedf334f7785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-network-check-target-ip-10-0-128-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61343"
    uid: e7aecdce-8607-4d79-aa27-6865e10434df
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:31:29Z"
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.460081ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 924.566µs
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 1.664372ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 994.204µs
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 1.212755ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 974.65µs
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:01:29Z"
    - latency: 1.055492ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:00:29Z"
    - latency: 980.897µs
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:59:29Z"
    - latency: 1.256933ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:58:29Z"
    - latency: 938.102µs
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-network-check-target-ip-10-0-133-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61345"
    uid: dd40157b-b19e-4944-9516-ed7b38f2a2f8
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:31:29Z"
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.610968ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 2.284436ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 2.402539ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 2.429102ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 2.384675ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 2.800062ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:01:29Z"
    - latency: 2.368145ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:00:29Z"
    - latency: 2.571633ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:59:29Z"
    - latency: 2.380265ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:58:29Z"
    - latency: 2.235427ms
      message: 'network-check-target-ip-10-0-133-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-network-check-target-ip-10-0-136-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61344"
    uid: 5206ef15-a6f8-4e3e-8476-c337b0594838
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:31:29Z"
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051316ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 1.752232ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 1.904104ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 1.781027ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 2.078066ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 2.409082ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:01:29Z"
    - latency: 2.177425ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:00:29Z"
    - latency: 1.936233ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:59:29Z"
    - latency: 2.135882ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:58:29Z"
    - latency: 1.782402ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T15:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-22-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-22.ec2.internal
      uid: 41f46092-1d4b-4faf-9677-53e503000cc5
    resourceVersion: "61346"
    uid: 39787e54-e359-4fed-9bcc-3f27be1785e3
  spec:
    sourcePod: network-check-source-869dcfcdcd-t4h7n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:30:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 1.923132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:06:29Z"
    - latency: 1.34294ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 1.763731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:05:29Z"
    - latency: 852.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 2.330149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:04:29Z"
    - latency: 1.072215ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 2.374508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:03:29Z"
    - latency: 877.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:02:29Z"
    - latency: 1.889306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:02:29Z"
kind: List
metadata:
  resourceVersion: ""