apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "63515"
    uid: 93f2056c-4da4-4a29-9341-21c520ea9c48
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:43:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.20863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 1.205694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 1.172849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 1.401911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:30Z"
    - latency: 1.176937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:07:30Z"
    - latency: 1.669033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:06:30Z"
    - latency: 1.596257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:05:30Z"
    - latency: 1.397366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:04:30Z"
    - latency: 1.340071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:03:30Z"
    - latency: 1.752966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "65321"
    uid: f76efa63-5d59-4625-bf70-3c83fd0706bc
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:42:30Z"
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.122988ms
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 7.827031ms
      message: 'load-balancer-api-external: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 14.363985ms
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 7.152911ms
      message: 'load-balancer-api-external: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 18.985849ms
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 6.58406ms
      message: 'load-balancer-api-external: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 17.174275ms
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 7.227518ms
      message: 'load-balancer-api-external: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 17.828008ms
      message: 'load-balancer-api-external: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:30Z"
    - latency: 6.618911ms
      message: 'load-balancer-api-external: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:08:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "65322"
    uid: d614a628-69c8-4a51-82a4-0ea16cad9a5a
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:42:30Z"
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.540987ms
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 7.848709ms
      message: 'load-balancer-api-internal: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 15.279662ms
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 7.2457ms
      message: 'load-balancer-api-internal: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 17.248563ms
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 6.611659ms
      message: 'load-balancer-api-internal: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 18.093584ms
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 7.27256ms
      message: 'load-balancer-api-internal: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 17.910491ms
      message: 'load-balancer-api-internal: tcp connection to ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:30Z"
    - latency: 6.596911ms
      message: 'load-balancer-api-internal: resolved host name ac87ffe8d451a468b971627518fb67d9-0b993e099be1e94a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:08:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-network-check-target-ip-10-0-136-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "69532"
    uid: e9eb6c09-6992-4fdc-ba6e-50d840e33d3b
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:49:59Z"
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296941ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:59Z"
    - latency: 2.272842ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:59Z"
    - latency: 2.04163ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:59Z"
    - latency: 5.983561ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:59Z"
    - latency: 2.395047ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:59Z"
    - latency: 2.46462ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:59Z"
    - latency: 2.501569ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:59Z"
    - latency: 2.489277ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:59Z"
    - latency: 2.459433ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:59Z"
    - latency: 2.400254ms
      message: 'network-check-target-ip-10-0-136-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-network-check-target-ip-10-0-136-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "63514"
    uid: c3b9ed3b-17e6-454b-89c2-0b6464c29aeb
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:43:30Z"
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.523818ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 1.138116ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 1.638803ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 1.067687ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:30Z"
    - latency: 1.425842ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:07:30Z"
    - latency: 2.18745ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:06:30Z"
    - latency: 1.228583ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:05:30Z"
    - latency: 1.42731ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:04:30Z"
    - latency: 1.282944ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:03:30Z"
    - latency: 1.41856ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:42:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-network-check-target-ip-10-0-139-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "69470"
    uid: 949bfee6-bb68-4e25-a8d8-ad69176871ff
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:49:51Z"
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.707276ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:51Z"
    - latency: 2.74726ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:51Z"
    - latency: 2.4357ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:51Z"
    - latency: 2.356149ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:51Z"
    - latency: 2.728943ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:51Z"
    - latency: 9.517946ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:51Z"
    - latency: 2.619954ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:51Z"
    - latency: 2.439502ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:51Z"
    - latency: 2.212205ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:51Z"
    - latency: 2.013809ms
      message: 'network-check-target-ip-10-0-139-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-228.ec2.internal
      uid: 8b93b25e-6d77-4ef3-a502-adbd1b708002
    resourceVersion: "65320"
    uid: 62ac4a64-0526-41e5-8490-7fd948a71e62
  spec:
    sourcePod: network-check-source-6f78d59f99-mms8d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:42:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.466805ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 2.024438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:12:30Z"
    - latency: 2.214844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 1.980452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:11:30Z"
    - latency: 2.152317ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 2.042574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:10:30Z"
    - latency: 989.939µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 2.177516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:09:30Z"
    - latency: 2.246226ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:08:30Z"
    - latency: 1.949511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:08:30Z"
kind: List
metadata:
  resourceVersion: ""