apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "54792"
    uid: 2427057a-9fe8-489b-a3c1-fe1617f4e3db
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:40:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.671704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 2.205864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 1.301422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 1.32166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 1.268744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:04:20Z"
    - latency: 986.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:03:20Z"
    - latency: 2.60032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:02:20Z"
    - latency: 1.789883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:01:20Z"
    - latency: 1.124292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:00:20Z"
    - latency: 1.205578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T01:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "55743"
    uid: b6984566-3177-4583-bbf1-663c8fc0760e
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:39:20Z"
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.414192ms
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 10.209052ms
      message: 'load-balancer-api-external: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 4.868143ms
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 10.582981ms
      message: 'load-balancer-api-external: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 4.869504ms
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 9.953887ms
      message: 'load-balancer-api-external: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 5.655188ms
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 10.324787ms
      message: 'load-balancer-api-external: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 5.822675ms
      message: 'load-balancer-api-external: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 10.420422ms
      message: 'load-balancer-api-external: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "55744"
    uid: 5ab85172-1b5d-48f1-adac-12fca3afc2d0
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:39:20Z"
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.139221ms
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 10.149553ms
      message: 'load-balancer-api-internal: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 4.883688ms
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 10.652095ms
      message: 'load-balancer-api-internal: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 3.620631ms
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 10.052041ms
      message: 'load-balancer-api-internal: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 5.676156ms
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 10.287832ms
      message: 'load-balancer-api-internal: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 5.80955ms
      message: 'load-balancer-api-internal: tcp connection to ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 10.582765ms
      message: 'load-balancer-api-internal: resolved host name ad7d267736d344664a3736a52e8b5e56-49d5e0547e8b42d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-network-check-target-ip-10-0-128-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "54789"
    uid: da68e0fd-7b8e-464f-9ad3-addcf4d6a19e
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:40:20Z"
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.305ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 1.174786ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 1.700414ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 1.399293ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 1.617334ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:04:20Z"
    - latency: 2.042662ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:03:20Z"
    - latency: 9.159886ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:02:20Z"
    - latency: 871.511µs
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:01:20Z"
    - latency: 1.672862ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:00:20Z"
    - latency: 1.192179ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T01:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-network-check-target-ip-10-0-133-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "54790"
    uid: 317e1555-3587-4691-820b-1e7ba4719c95
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:40:20Z"
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.842093ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 2.658108ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 3.025344ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 2.830393ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 3.381906ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:04:20Z"
    - latency: 2.950554ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:03:20Z"
    - latency: 8.664699ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:02:20Z"
    - latency: 2.581872ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:01:20Z"
    - latency: 3.324651ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:00:20Z"
    - latency: 2.580764ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T01:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-network-check-target-ip-10-0-139-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "54791"
    uid: fd3eb27f-dd64-44cb-b818-ad0dbcd2ce79
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:40:20Z"
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.993635ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 3.1011ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 3.675925ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 2.841195ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 3.092119ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:04:20Z"
    - latency: 2.402796ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:03:20Z"
    - latency: 8.788858ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:02:20Z"
    - latency: 2.620833ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:01:20Z"
    - latency: 2.705618ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:00:20Z"
    - latency: 3.268088ms
      message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T01:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T01:33:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-8.ec2.internal
      uid: ec7eae52-6f7a-485a-8beb-52e455a03826
    resourceVersion: "55742"
    uid: 55a5c9dd-d43e-42ae-9105-4ced22c0913e
  spec:
    sourcePod: network-check-source-989f8b8dc-b7ltw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T01:39:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.416µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 2.900094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:09:20Z"
    - latency: 1.235782ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 3.214351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:08:20Z"
    - latency: 1.253393ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 2.277161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:07:20Z"
    - latency: 1.031123ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 2.38586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:06:20Z"
    - latency: 1.800831ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T02:05:20Z"
    - latency: 1.957185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T02:05:20Z"
kind: List
metadata:
  resourceVersion: ""