apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "18511"
    uid: 532ff0f2-6f09-412d-8b1e-2989f7da0298
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:57:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 1.362834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:03:07Z"
    - latency: 1.462955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:02:07Z"
    - latency: 1.096389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:01:07Z"
    - latency: 1.055953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:00:07Z"
    - latency: 796.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:59:07Z"
    - latency: 925.122µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:58:07Z"
    - latency: 1.024335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:57:07Z"
    - latency: 1.191633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:56:07Z"
    - latency: 1.012605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:55:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "20624"
    uid: 2c616891-1ed4-43d6-b20a-d50d5d4a6df2
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:56:07Z"
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.79611ms
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 9.099405ms
      message: 'load-balancer-api-external: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 4.797846ms
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 8.782956ms
      message: 'load-balancer-api-external: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 4.933296ms
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 7.320583ms
      message: 'load-balancer-api-external: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 5.966324ms
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 8.443553ms
      message: 'load-balancer-api-external: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 4.625534ms
      message: 'load-balancer-api-external: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 7.717515ms
      message: 'load-balancer-api-external: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "20623"
    uid: 6e960f76-5f52-41f6-953f-e78943dd334c
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:56:07Z"
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.77108ms
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 9.044184ms
      message: 'load-balancer-api-internal: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 4.828603ms
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 8.706004ms
      message: 'load-balancer-api-internal: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 5.140495ms
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 7.283096ms
      message: 'load-balancer-api-internal: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 5.645802ms
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 8.360253ms
      message: 'load-balancer-api-internal: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 4.60434ms
      message: 'load-balancer-api-internal: tcp connection to ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 7.661118ms
      message: 'load-balancer-api-internal: resolved host name ac9840589403b444a8cb6557de5532f0-b4dfef9e8613c064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-128-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "18508"
    uid: c3b3ac98-b4da-451a-9872-c36ea8d9007d
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:57:07Z"
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.773589ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 1.941146ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:03:07Z"
    - latency: 1.850004ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:02:07Z"
    - latency: 1.624781ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:01:07Z"
    - latency: 1.984688ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:00:07Z"
    - latency: 2.095202ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:59:07Z"
    - latency: 1.865265ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:58:07Z"
    - latency: 1.667815ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:57:07Z"
    - latency: 2.011091ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:56:07Z"
    - latency: 1.431711ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:55:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-133-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "18509"
    uid: f1158a6d-ab99-407f-a0d4-14dbd58957b1
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:57:07Z"
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.481µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 815.875µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:03:07Z"
    - latency: 964.482µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:02:07Z"
    - latency: 839.875µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:01:07Z"
    - latency: 1.13695ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:00:07Z"
    - latency: 877.982µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:59:07Z"
    - latency: 791.192µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:58:07Z"
    - latency: 836.092µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:57:07Z"
    - latency: 1.28348ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:56:07Z"
    - latency: 752.242µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:55:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-136-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "18510"
    uid: 9fd28d7e-b8a8-42a4-b1c8-3500aba0d12d
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:57:07Z"
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.997369ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 2.169451ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:03:07Z"
    - latency: 2.230444ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:02:07Z"
    - latency: 1.972678ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:01:07Z"
    - latency: 2.160645ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:00:07Z"
    - latency: 2.040234ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:59:07Z"
    - latency: 1.884244ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:58:07Z"
    - latency: 2.079882ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:57:07Z"
    - latency: 2.149ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:56:07Z"
    - latency: 1.901484ms
      message: 'network-check-target-ip-10-0-136-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:55:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:50:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: dd8e492c-0318-4f34-bb0a-c6c36df45c77
    resourceVersion: "20622"
    uid: 0f1393ef-4ef4-415d-9bd8-8747eba14906
  spec:
    sourcePod: network-check-source-8894fc9bd-kxklx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:56:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.008637ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 1.951559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:08:07Z"
    - latency: 929.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 1.991112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:07:07Z"
    - latency: 806.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 1.824509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:06:07Z"
    - latency: 1.079887ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 2.031871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:05:07Z"
    - latency: 829.75µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:04:07Z"
    - latency: 1.624907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:04:07Z"
kind: List
metadata:
  resourceVersion: ""