apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "21214"
    uid: 127b493d-05ea-435c-8387-25ab455df294
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.33µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:48Z"
    - latency: 1.01132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:48Z"
    - latency: 1.026525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:48Z"
    - latency: 761.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 967.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 951.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 991.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 1.328647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 849.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:48Z"
    - latency: 861.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "19880"
    uid: fd0229e2-a60d-4aa0-bdf9-ac40dfe06f4a
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:55:48Z"
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.30553ms
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 7.923976ms
      message: 'load-balancer-api-external: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 11.23247ms
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 8.721572ms
      message: 'load-balancer-api-external: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 5.558676ms
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 7.859321ms
      message: 'load-balancer-api-external: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 6.089602ms
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 8.591565ms
      message: 'load-balancer-api-external: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 4.218632ms
      message: 'load-balancer-api-external: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 9.337712ms
      message: 'load-balancer-api-external: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "19879"
    uid: c278594f-e23b-456b-adb4-ee85f03d704a
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:55:48Z"
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.346036ms
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 7.852181ms
      message: 'load-balancer-api-internal: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 11.282657ms
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 8.625878ms
      message: 'load-balancer-api-internal: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 5.570917ms
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 7.776099ms
      message: 'load-balancer-api-internal: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 6.07854ms
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 8.507152ms
      message: 'load-balancer-api-internal: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 4.013975ms
      message: 'load-balancer-api-internal: tcp connection to adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 9.350511ms
      message: 'load-balancer-api-internal: resolved host name adb584a16b9d24581948098a2dfd170d-8127af5ed5b700fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-128-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "21211"
    uid: e0a1cea8-75aa-4a77-98f7-02b4ade52523
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:48Z"
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206303ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:48Z"
    - latency: 2.662998ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:48Z"
    - latency: 2.331473ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:48Z"
    - latency: 2.3285ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 2.048724ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 2.275034ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 2.287316ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 2.468757ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 2.439818ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:48Z"
    - latency: 2.440779ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-133-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "21210"
    uid: 30588d6c-108e-4a2c-ae5f-f5aa0731b040
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:48Z"
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.446µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:48Z"
    - latency: 853.567µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:48Z"
    - latency: 857.367µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:48Z"
    - latency: 923.228µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 1.338515ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 1.245727ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 1.229859ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 1.089842ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 817.047µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:48Z"
    - latency: 894.486µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-137-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "21212"
    uid: 50c33f14-e6eb-42c2-89cc-00de79dcbdea
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:48Z"
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.616526ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:48Z"
    - latency: 2.389488ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:48Z"
    - latency: 2.035563ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:48Z"
    - latency: 2.165414ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 2.057412ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 2.1493ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 2.347588ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 2.33093ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 2.535982ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:48Z"
    - latency: 2.018626ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 13580fc2-0606-44e6-bf75-0af1a43e6daf
    resourceVersion: "19877"
    uid: e4fd71db-3a84-4b65-9750-31913d3308d0
  spec:
    sourcePod: network-check-source-989f8b8dc-9v7lb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:55:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.89µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 1.488712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:48Z"
    - latency: 897.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 1.867097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:48Z"
    - latency: 905.58µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 1.572929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:48Z"
    - latency: 863.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 1.972769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:48Z"
    - latency: 836.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:48Z"
    - latency: 1.879397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:48Z"
kind: List
metadata:
  resourceVersion: ""