apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60215"
    uid: f51c63d1-9764-4237-8ae9-2e05e54b999b
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:00:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.576818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 1.13824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 1.02177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 923.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 1.585964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 978.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:30:28Z"
    - latency: 873.508µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:29:28Z"
    - latency: 884.232µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:28:28Z"
    - latency: 1.114398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:27:28Z"
    - latency: 986.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:26:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60217"
    uid: de9b4d9e-f766-41b0-98c9-3b6370669e1a
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:59:28Z"
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.605088ms
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 7.006972ms
      message: 'load-balancer-api-external: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 7.974591ms
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 6.168068ms
      message: 'load-balancer-api-external: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 3.499337ms
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 7.0333ms
      message: 'load-balancer-api-external: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 5.420376ms
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 6.558074ms
      message: 'load-balancer-api-external: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 3.568805ms
      message: 'load-balancer-api-external: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 6.603329ms
      message: 'load-balancer-api-external: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:31:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60218"
    uid: b01759fc-7664-4549-96b1-e2c219f8a7e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:59:28Z"
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.576007ms
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 7.033246ms
      message: 'load-balancer-api-internal: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 3.504287ms
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 6.133024ms
      message: 'load-balancer-api-internal: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 3.545514ms
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 6.970601ms
      message: 'load-balancer-api-internal: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 5.429554ms
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 6.471698ms
      message: 'load-balancer-api-internal: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 3.591145ms
      message: 'load-balancer-api-internal: tcp connection to ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 6.652105ms
      message: 'load-balancer-api-internal: resolved host name ad8aa915f7eec4c37a14e37ce5a2d041-30d39cd53e8bbe9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:31:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-network-check-target-ip-10-0-129-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60211"
    uid: 48356897-8224-40d4-9ccd-bf42ddd7370c
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:00:28Z"
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.449582ms
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 1.058031ms
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 943.009µs
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 977.967µs
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 932.263µs
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 1.011333ms
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:30:28Z"
    - latency: 1.394655ms
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:29:28Z"
    - latency: 1.164207ms
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:28:28Z"
    - latency: 912.688µs
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:27:28Z"
    - latency: 863.371µs
      message: 'network-check-target-ip-10-0-129-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:26:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-network-check-target-ip-10-0-137-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60214"
    uid: ceb7ba77-7f12-42ed-bab6-c7610e3e71a6
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:00:28Z"
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446839ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 2.62343ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 2.329698ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 2.494497ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 2.277042ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 2.454006ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:30:28Z"
    - latency: 2.317929ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:29:28Z"
    - latency: 2.159859ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:28:28Z"
    - latency: 2.187524ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:27:28Z"
    - latency: 2.871749ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:26:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-network-check-target-ip-10-0-143-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60212"
    uid: 751804ad-0a0f-4c00-a5b3-8081ac1c5e47
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:00:28Z"
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.392138ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 2.426872ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 2.344207ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 2.182123ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 2.321219ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 2.377962ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:30:28Z"
    - latency: 2.739238ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:29:28Z"
    - latency: 2.235209ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:28:28Z"
    - latency: 2.603057ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:27:28Z"
    - latency: 2.568701ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:26:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:53:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-218.ec2.internal
      uid: ae7532cf-ab35-4a15-a376-f8d68a7a50da
    resourceVersion: "60213"
    uid: 7227dc2f-5588-402a-8a49-1f9f1b892f14
  spec:
    sourcePod: network-check-source-869dcfcdcd-262pn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:59:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 2.16045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:35:28Z"
    - latency: 1.287396ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 1.734783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:34:28Z"
    - latency: 1.08208ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 2.083669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:33:28Z"
    - latency: 844.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 1.672082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:32:28Z"
    - latency: 1.296109ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:31:28Z"
    - latency: 1.916745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:31:28Z"
kind: List
metadata:
  resourceVersion: ""