apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "119226"
    uid: e36a9561-0942-4071-8412-cb6cf7f8a9dc
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:23:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 1.238578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 1.132869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 1.515358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:23:06Z"
    - latency: 918.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:22:06Z"
    - latency: 1.661641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:21:06Z"
    - latency: 1.267315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:20:06Z"
    - latency: 1.964048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:19:06Z"
    - latency: 1.137629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:18:06Z"
    - latency: 972.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "121448"
    uid: 7505fb2c-fb2b-4698-949b-3a619a7839bf
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:22:06Z"
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.785369ms
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 7.956484ms
      message: 'load-balancer-api-external: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 50.984934ms
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 11.039664ms
      message: 'load-balancer-api-external: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 54.64694ms
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 7.140931ms
      message: 'load-balancer-api-external: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 50.84698ms
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 9.213524ms
      message: 'load-balancer-api-external: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 54.178886ms
      message: 'load-balancer-api-external: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 11.17929ms
      message: 'load-balancer-api-external: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "121447"
    uid: 0c57acf9-d6ee-4338-84c8-0bd664acfbbc
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:22:06Z"
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.800768ms
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 7.85754ms
      message: 'load-balancer-api-internal: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 53.292702ms
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 11.08888ms
      message: 'load-balancer-api-internal: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 54.913321ms
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 7.208338ms
      message: 'load-balancer-api-internal: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 51.361364ms
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 9.176234ms
      message: 'load-balancer-api-internal: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 50.521702ms
      message: 'load-balancer-api-internal: tcp connection to aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 11.111839ms
      message: 'load-balancer-api-internal: resolved host name aa4a48b711f844547b37f00e18a10669-41cfdfea4362ef04.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-network-check-target-ip-10-0-130-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "119222"
    uid: 6ea3487f-5c27-4f54-9b05-91d385bd92b8
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:23:06Z"
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.817µs
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 993.232µs
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 1.664024ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 1.67685ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:23:06Z"
    - latency: 811.212µs
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:22:06Z"
    - latency: 1.033738ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:21:06Z"
    - latency: 926.183µs
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:20:06Z"
    - latency: 1.059028ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:19:06Z"
    - latency: 1.039285ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:18:06Z"
    - latency: 961.397µs
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-network-check-target-ip-10-0-133-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "119224"
    uid: d455e23a-11d4-4457-9d22-710e5757d2d8
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:23:06Z"
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.566973ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 2.312253ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 1.933071ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 2.009162ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:23:06Z"
    - latency: 1.772282ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:22:06Z"
    - latency: 1.873153ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:21:06Z"
    - latency: 2.117907ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:20:06Z"
    - latency: 2.10598ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:19:06Z"
    - latency: 1.793059ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:18:06Z"
    - latency: 1.881886ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-network-check-target-ip-10-0-137-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "119223"
    uid: 4c5bbf85-efe6-42ef-9367-310d878fd19b
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:23:06Z"
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.165669ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 2.548748ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 2.419985ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 2.374328ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:23:06Z"
    - latency: 1.841013ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:22:06Z"
    - latency: 2.129264ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:21:06Z"
    - latency: 2.292658ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:20:06Z"
    - latency: 2.097824ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:19:06Z"
    - latency: 2.071903ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:18:06Z"
    - latency: 1.782327ms
      message: 'network-check-target-ip-10-0-137-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T21:16:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-83.us-west-2.compute.internal
      uid: 963a005a-ca77-41c9-9c8a-3c149a9fb866
    resourceVersion: "121445"
    uid: 449223c9-5d9e-4b1f-bbf1-b722be3ce15e
  spec:
    sourcePod: network-check-source-6f78d59f99-l4hv8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T21:22:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 2.005015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:28:06Z"
    - latency: 988.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 2.201286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:27:06Z"
    - latency: 933.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 1.838192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:26:06Z"
    - latency: 1.096087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 1.874229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:25:06Z"
    - latency: 977.992µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:24:06Z"
    - latency: 1.963764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:24:06Z"
kind: List
metadata:
  resourceVersion: ""