apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "39008"
    uid: 7df970ed-1a52-4ee9-9ad1-18e0450015db
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.809121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:27Z"
    - latency: 1.187379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 1.067097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 915.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 1.173432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 896.299µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 1.189164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:36:27Z"
    - latency: 979.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:35:27Z"
    - latency: 1.920786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:27Z"
    - latency: 1.008184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "38384"
    uid: 925e8610-f01e-4d6c-a318-ddeb3c51d2f1
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:27Z"
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.17533ms
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 8.834927ms
      message: 'load-balancer-api-external: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 4.681248ms
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 9.005995ms
      message: 'load-balancer-api-external: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 5.755337ms
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 8.262926ms
      message: 'load-balancer-api-external: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 5.219257ms
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 8.177905ms
      message: 'load-balancer-api-external: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 4.993731ms
      message: 'load-balancer-api-external: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 9.160038ms
      message: 'load-balancer-api-external: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:37:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "38383"
    uid: 271ccd9a-6ac4-4f9f-b294-de8974851fc0
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:27Z"
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.699132ms
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 8.808052ms
      message: 'load-balancer-api-internal: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 4.637099ms
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 9.042354ms
      message: 'load-balancer-api-internal: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 5.363435ms
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 8.232801ms
      message: 'load-balancer-api-internal: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 4.617723ms
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 8.27179ms
      message: 'load-balancer-api-internal: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 5.007586ms
      message: 'load-balancer-api-internal: tcp connection to a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 9.10684ms
      message: 'load-balancer-api-internal: resolved host name a815be129c69c4bbaaaacf85a0603b70-26f6cbb17af0e78a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:37:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-129-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "39006"
    uid: 95a3599b-f068-4939-893b-049202684981
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:27Z"
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286673ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:27Z"
    - latency: 2.404905ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 2.163316ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 2.288816ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 2.203551ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 2.289632ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 1.980519ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:36:27Z"
    - latency: 2.428164ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:35:27Z"
    - latency: 2.3666ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:27Z"
    - latency: 2.315205ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-131-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "39005"
    uid: 843b4cfc-0d2a-48ff-b04b-510c57f6ba93
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:27Z"
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.465µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:27Z"
    - latency: 1.018532ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 1.068159ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 861.334µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 956.769µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 1.020993ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 977.704µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:36:27Z"
    - latency: 1.148005ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:35:27Z"
    - latency: 1.354796ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:27Z"
    - latency: 1.100153ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-143-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "39007"
    uid: 389df873-2884-4294-afc6-694499d0c1df
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:00:27Z"
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.699899ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:42:27Z"
    - latency: 1.97974ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 2.008547ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 2.265447ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 2.085385ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 2.140343ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 2.351247ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:36:27Z"
    - latency: 2.003182ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:35:27Z"
    - latency: 2.488493ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:27Z"
    - latency: 2.026542ms
      message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:53:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: 0909764c-544c-43da-a594-1682b51b6b4a
    resourceVersion: "38382"
    uid: ba094b7c-e13a-4853-b3de-ea9a3b6be2c8
  spec:
    sourcePod: network-check-source-7cbc45fddc-8g7bq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.99µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 2.007309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:41:27Z"
    - latency: 895.832µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 2.137998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:40:27Z"
    - latency: 819.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 1.829857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:39:27Z"
    - latency: 1.100765ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 1.783632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:38:27Z"
    - latency: 979.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:37:27Z"
    - latency: 1.814939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:37:27Z"
kind: List
metadata:
  resourceVersion: ""