apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "54225"
    uid: 7e5b8415-8b9a-4277-a766-68a53e4ca1fd
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:00:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 1.846732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 997.908µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 890.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 1.007769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:45Z"
    - latency: 867.258µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:45Z"
    - latency: 1.266026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:45Z"
    - latency: 1.374199ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:45Z"
    - latency: 802.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:45Z"
    - latency: 1.115472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "55223"
    uid: f2e1d2fb-be63-4f56-a6bd-3b19e82b11fc
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:45Z"
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.453853ms
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 9.652925ms
      message: 'load-balancer-api-external: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 3.954228ms
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 8.704318ms
      message: 'load-balancer-api-external: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 3.937522ms
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 9.424194ms
      message: 'load-balancer-api-external: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 3.63787ms
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 8.473253ms
      message: 'load-balancer-api-external: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 5.538591ms
      message: 'load-balancer-api-external: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 6.962369ms
      message: 'load-balancer-api-external: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "55222"
    uid: 31a60430-feb3-46ed-b00f-5a60dacd3ed0
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:45Z"
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.41899ms
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 9.714661ms
      message: 'load-balancer-api-internal: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 3.933328ms
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 8.790155ms
      message: 'load-balancer-api-internal: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 3.82185ms
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 9.784146ms
      message: 'load-balancer-api-internal: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 4.283154ms
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 8.543149ms
      message: 'load-balancer-api-internal: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 3.858858ms
      message: 'load-balancer-api-internal: tcp connection to a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 6.883289ms
      message: 'load-balancer-api-internal: resolved host name a879c76c44097480a81b09667282bf78-c292afb86139bb42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-network-check-target-ip-10-0-128-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "54223"
    uid: 17738670-e056-4fd9-a7f9-0b68c7c7fcaa
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:00:45Z"
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.1907ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 1.723716ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 2.242309ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 2.148579ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 2.660334ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:45Z"
    - latency: 2.025552ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:45Z"
    - latency: 2.279211ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:45Z"
    - latency: 2.6974ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:45Z"
    - latency: 2.299543ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:45Z"
    - latency: 2.176255ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-network-check-target-ip-10-0-130-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "54224"
    uid: 79516d64-2c90-496b-96d5-cc32ad630930
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:00:45Z"
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.85602ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 2.169463ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 1.842199ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 2.002934ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 2.17908ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:45Z"
    - latency: 2.153359ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:45Z"
    - latency: 2.41907ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:45Z"
    - latency: 1.974003ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:45Z"
    - latency: 1.885935ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:45Z"
    - latency: 2.591143ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-network-check-target-ip-10-0-132-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "54222"
    uid: 2280f292-fef2-482b-bc8e-9f6f4a13049c
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:00:45Z"
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.813µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 774.3µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 1.223905ms
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 768.789µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 1.457951ms
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:45Z"
    - latency: 905.584µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:45Z"
    - latency: 967.377µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:45Z"
    - latency: 1.033584ms
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:45Z"
    - latency: 820.795µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:45Z"
    - latency: 866.195µs
      message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:53:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-202.ec2.internal
      uid: 574ab3db-4700-4de8-912e-4df307db0702
    resourceVersion: "55218"
    uid: 754f81e3-0e60-4a81-88db-3e579cc6212a
  spec:
    sourcePod: network-check-source-989f8b8dc-jt9g6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.972µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 1.7193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:29:45Z"
    - latency: 774.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 1.843215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:45Z"
    - latency: 994.95µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 2.246393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:45Z"
    - latency: 673.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 1.897188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:45Z"
    - latency: 1.160145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:45Z"
    - latency: 1.544958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:45Z"
kind: List
metadata:
  resourceVersion: ""