apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "42573"
    uid: e60ed99a-7273-4ffa-aa58-e343bc83929f
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:48:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 1.006556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 1.209445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 1.072424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:06:00Z"
    - latency: 1.010863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:05:00Z"
    - latency: 957.093µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:04:00Z"
    - latency: 1.007832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:03:00Z"
    - latency: 955.579µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:02:00Z"
    - latency: 1.107019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:01:00Z"
    - latency: 950.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "44749"
    uid: fe53cd9b-7c9f-4f86-9841-1259b67df30d
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:47:00Z"
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.091518ms
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 8.744832ms
      message: 'load-balancer-api-external: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 3.815166ms
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 8.273652ms
      message: 'load-balancer-api-external: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 4.181312ms
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 11.301439ms
      message: 'load-balancer-api-external: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 3.386483ms
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 9.499942ms
      message: 'load-balancer-api-external: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 17.735864ms
      message: 'load-balancer-api-external: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 8.497234ms
      message: 'load-balancer-api-external: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "44750"
    uid: 88c88398-273c-4273-83fb-0d0c304fd385
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:47:00Z"
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.092847ms
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 8.694988ms
      message: 'load-balancer-api-internal: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 3.987426ms
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 8.302821ms
      message: 'load-balancer-api-internal: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 4.159784ms
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 11.408424ms
      message: 'load-balancer-api-internal: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 4.210548ms
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 9.44672ms
      message: 'load-balancer-api-internal: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 16.312378ms
      message: 'load-balancer-api-internal: tcp connection to a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 8.52098ms
      message: 'load-balancer-api-internal: resolved host name a8a1a2fb79bd644ff9621bc2c7071af3-93a4ca200dcec420.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-129-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "42569"
    uid: 030a6d34-3c25-49a8-85d5-d2d550ce6068
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:48:00Z"
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.507µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 783.712µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 1.479656ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 1.473069ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:06:00Z"
    - latency: 878.918µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:05:00Z"
    - latency: 895.611µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:04:00Z"
    - latency: 854.681µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:03:00Z"
    - latency: 1.303087ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:02:00Z"
    - latency: 829.546µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:01:00Z"
    - latency: 799.922µs
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-132-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "42572"
    uid: ddebd333-7cde-4bfb-84ed-f407fa67bdc1
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:48:00Z"
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.839606ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 2.001078ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 2.038946ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 2.22547ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:06:00Z"
    - latency: 2.255096ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:05:00Z"
    - latency: 2.073657ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:04:00Z"
    - latency: 2.297886ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:03:00Z"
    - latency: 2.244546ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:02:00Z"
    - latency: 2.302052ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:01:00Z"
    - latency: 2.239517ms
      message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-network-check-target-ip-10-0-140-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "42571"
    uid: 50232909-1650-4fc8-9cf6-4b9e61197097
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:48:00Z"
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.055474ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 1.761451ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 2.136841ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 1.80805ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:06:00Z"
    - latency: 1.909485ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:05:00Z"
    - latency: 1.703992ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:04:00Z"
    - latency: 1.875135ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:03:00Z"
    - latency: 1.877628ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:02:00Z"
    - latency: 2.157268ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:01:00Z"
    - latency: 1.853561ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:40:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-1.ec2.internal
      uid: 0ced31c0-0c67-49cd-982d-b55dd509a402
    resourceVersion: "44746"
    uid: 4991d029-5804-47c8-801e-90e12f426b47
  spec:
    sourcePod: network-check-source-7f44b6dd87-cktgt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:47:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 1.790506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:11:00Z"
    - latency: 821.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 1.69503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:10:00Z"
    - latency: 921.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 1.649875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:09:00Z"
    - latency: 924.953µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 1.77402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:08:00Z"
    - latency: 1.121308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:07:00Z"
    - latency: 1.738493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:07:00Z"
kind: List
metadata:
  resourceVersion: ""