apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "21858"
    uid: 7ba350a4-ea8c-41f2-acc3-af3c913866ad
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:46:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:07:49Z"
    - latency: 903.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:06:49Z"
    - latency: 892.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:05:49Z"
    - latency: 868.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:04:49Z"
    - latency: 860.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 1.271288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 1.205177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 931.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 1.018455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 853.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "20170"
    uid: 70f2e5e0-530d-4a34-82c7-f90213832c30
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:45:49Z"
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.653044ms
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 8.72951ms
      message: 'load-balancer-api-external: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 7.634799ms
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 8.338312ms
      message: 'load-balancer-api-external: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 5.900312ms
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 9.906414ms
      message: 'load-balancer-api-external: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 5.512427ms
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 8.672975ms
      message: 'load-balancer-api-external: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 6.079846ms
      message: 'load-balancer-api-external: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 13.942034ms
      message: 'load-balancer-api-external: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T11:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "20169"
    uid: a417e465-b61d-4534-b635-7f2c9224b65b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:45:49Z"
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.239315ms
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 8.709439ms
      message: 'load-balancer-api-internal: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 5.147616ms
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 8.313985ms
      message: 'load-balancer-api-internal: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 6.392973ms
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 9.962621ms
      message: 'load-balancer-api-internal: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 14.86214ms
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 8.59694ms
      message: 'load-balancer-api-internal: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 5.450998ms
      message: 'load-balancer-api-internal: tcp connection to a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 14.008917ms
      message: 'load-balancer-api-internal: resolved host name a43e656b376c9484e98e6bd4a59b39ec-98dc64f879941a57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T11:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-network-check-target-ip-10-0-130-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "21856"
    uid: 03514b45-d280-4abf-b08a-ffb9b27ce005
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:46:49Z"
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.642975ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:07:49Z"
    - latency: 1.70026ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:06:49Z"
    - latency: 1.803976ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:05:49Z"
    - latency: 1.770403ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:04:49Z"
    - latency: 1.620043ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 1.664288ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 1.804084ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 1.657341ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 1.962358ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 1.791624ms
      message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-network-check-target-ip-10-0-132-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "21855"
    uid: b393f7f6-983d-476a-bd3d-49a24abd1779
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:46:49Z"
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 792.247µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:07:49Z"
    - latency: 983.513µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:06:49Z"
    - latency: 902.888µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:05:49Z"
    - latency: 779.574µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:04:49Z"
    - latency: 833.388µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 1.03342ms
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 1.649095ms
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 912.019µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 3.45871ms
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 781.571µs
      message: 'network-check-target-ip-10-0-132-210: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-network-check-target-ip-10-0-139-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "21857"
    uid: 48a4483c-63b1-47b4-84f0-697cb8b67868
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:46:49Z"
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.831898ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:07:49Z"
    - latency: 1.77275ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:06:49Z"
    - latency: 2.23814ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:05:49Z"
    - latency: 1.91564ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:04:49Z"
    - latency: 1.857684ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 2.181588ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 2.223903ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 2.216555ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 2.404508ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 1.730714ms
      message: 'network-check-target-ip-10-0-139-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-210.ec2.internal
      uid: b18f4ff7-13cd-4552-843e-3dabfb43ba2b
    resourceVersion: "20168"
    uid: 8a13742e-7e49-4097-bfaf-41f50d24cf65
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r64wt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:45:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 1.724441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:03:49Z"
    - latency: 952.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 1.877483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:02:49Z"
    - latency: 936.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 2.010443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:01:49Z"
    - latency: 1.418845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 1.709636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:00:49Z"
    - latency: 1.041459ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T11:59:49Z"
    - latency: 3.113733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T11:59:49Z"
kind: List
metadata:
  resourceVersion: ""