apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31949"
    uid: 1d866f45-c46f-4994-8c0d-7998faae46ec
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.344µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 906.833µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 1.279797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 1.163385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 1.340123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 963.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:51:00Z"
    - latency: 932.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:50:00Z"
    - latency: 1.102341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:49:00Z"
    - latency: 1.073559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:48:00Z"
    - latency: 1.2631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:47:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31950"
    uid: 0ff78d43-9844-490b-b1bc-881c4111051d
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:00Z"
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.419339ms
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 8.284611ms
      message: 'load-balancer-api-external: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 5.570735ms
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 7.99072ms
      message: 'load-balancer-api-external: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 3.983801ms
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 7.88452ms
      message: 'load-balancer-api-external: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 4.029147ms
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 8.598034ms
      message: 'load-balancer-api-external: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 3.711136ms
      message: 'load-balancer-api-external: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 8.503788ms
      message: 'load-balancer-api-external: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31951"
    uid: b3772e93-f274-4785-a22d-a73328e0d53f
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:00Z"
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.455676ms
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 8.204648ms
      message: 'load-balancer-api-internal: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 4.022576ms
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 8.075736ms
      message: 'load-balancer-api-internal: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 3.978368ms
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 7.905985ms
      message: 'load-balancer-api-internal: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 4.602ms
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 8.546424ms
      message: 'load-balancer-api-internal: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 3.721548ms
      message: 'load-balancer-api-internal: tcp connection to a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 8.627453ms
      message: 'load-balancer-api-internal: resolved host name a1beb7a0aa2ae46bd9d47566ffcb21fc-de87b0c521839dd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-128-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31947"
    uid: 3ebcb8ef-62de-45c7-ab8f-52876b65de92
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:00Z"
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044283ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 1.865107ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 1.907564ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 1.857828ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 1.893154ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 2.022203ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:51:00Z"
    - latency: 2.326217ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:50:00Z"
    - latency: 2.109427ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:49:00Z"
    - latency: 1.831272ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:48:00Z"
    - latency: 2.423286ms
      message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:47:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-137-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31945"
    uid: 147c9b87-e6eb-42c4-86eb-66b53f4a686e
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:00Z"
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.152µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 880.708µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 1.462409ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 822.924µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 1.126474ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 1.339742ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:51:00Z"
    - latency: 905.281µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:50:00Z"
    - latency: 1.323216ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:49:00Z"
    - latency: 845.485µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:48:00Z"
    - latency: 835.59µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:47:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-143-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31946"
    uid: 461b85de-6539-465d-a3cf-9f708bfefcca
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:00Z"
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.154232ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 2.070887ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 2.084298ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 2.030285ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 2.051172ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 1.966838ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:51:00Z"
    - latency: 1.970793ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:50:00Z"
    - latency: 2.134585ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:49:00Z"
    - latency: 1.889193ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:48:00Z"
    - latency: 1.971824ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:47:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:13:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: e7089121-a076-4ed0-a3e3-79d2b1f415c7
    resourceVersion: "31948"
    uid: 4a7e59c0-0931-46fc-97b8-79388ea61d17
  spec:
    sourcePod: network-check-source-7b678d77c7-h6q2h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28433ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 1.768683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:56:00Z"
    - latency: 777.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 1.923293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:55:00Z"
    - latency: 1.01156ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 1.831956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:54:00Z"
    - latency: 771.672µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 1.832245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:53:00Z"
    - latency: 819.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:52:00Z"
    - latency: 2.096549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:52:00Z"
kind: List
metadata:
  resourceVersion: ""