apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68005"
    uid: f8ed62fb-64cd-4b1e-8c1f-bd33a3ef7cac
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:08:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 921.472µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 1.744421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 1.09489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 1.05787ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:32:57Z"
    - latency: 1.356724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:31:57Z"
    - latency: 910.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:30:57Z"
    - latency: 808.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:29:57Z"
    - latency: 1.099868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:28:57Z"
    - latency: 916.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68913"
    uid: 42ffffa1-450e-471a-be62-854142a0fae0
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:07:57Z"
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.476704ms
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 9.442913ms
      message: 'load-balancer-api-external: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 6.102739ms
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 8.869048ms
      message: 'load-balancer-api-external: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 5.334693ms
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 7.538356ms
      message: 'load-balancer-api-external: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 3.999445ms
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 9.67276ms
      message: 'load-balancer-api-external: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 4.233264ms
      message: 'load-balancer-api-external: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 10.15509ms
      message: 'load-balancer-api-external: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:33:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68912"
    uid: e5a9138d-5621-4176-af83-546ccc2aa056
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:07:57Z"
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.498794ms
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 9.409044ms
      message: 'load-balancer-api-internal: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 8.178054ms
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 8.799216ms
      message: 'load-balancer-api-internal: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 5.359735ms
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 7.488199ms
      message: 'load-balancer-api-internal: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 4.027748ms
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 9.642317ms
      message: 'load-balancer-api-internal: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 4.895889ms
      message: 'load-balancer-api-internal: tcp connection to a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 10.07929ms
      message: 'load-balancer-api-internal: resolved host name a261d4f85cebe45628ae6f5a4d63d216-ec705fd0f8d7de4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:33:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-129-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68004"
    uid: 00d98a43-42df-45d0-93d3-ce0922235ccb
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:08:57Z"
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.140497ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 2.087274ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 2.23922ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 2.013919ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 2.18194ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:32:57Z"
    - latency: 1.863369ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:31:57Z"
    - latency: 2.076277ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:30:57Z"
    - latency: 2.585182ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:29:57Z"
    - latency: 1.857223ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:28:57Z"
    - latency: 2.063854ms
      message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-139-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68002"
    uid: 9b2986a7-4ffb-4247-a27b-51cdd1312c05
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:08:57Z"
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.696µs
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 1.081751ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 1.396163ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 1.04096ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 1.580202ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:32:57Z"
    - latency: 882.88µs
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:31:57Z"
    - latency: 1.249803ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:30:57Z"
    - latency: 1.084843ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:29:57Z"
    - latency: 791.725µs
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:28:57Z"
    - latency: 1.148899ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-143-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68003"
    uid: 42f24199-db82-43f5-87f1-7269c04ac880
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:08:57Z"
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.946472ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 2.184296ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 2.552652ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 2.367945ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 2.620334ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:32:57Z"
    - latency: 2.576897ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:31:57Z"
    - latency: 2.223223ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:30:57Z"
    - latency: 2.135536ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:29:57Z"
    - latency: 1.902802ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:28:57Z"
    - latency: 2.457162ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:01:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 8e384576-0d7d-481d-8b8e-b60377828474
    resourceVersion: "68914"
    uid: cd34e42c-7acb-4d26-9c88-3008c2b3357c
  spec:
    sourcePod: network-check-source-7cbc45fddc-dsbvp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T14:07:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 2.152523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:37:57Z"
    - latency: 955.474µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 2.219731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:36:57Z"
    - latency: 1.341636ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 1.791144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:35:57Z"
    - latency: 1.192913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 2.277081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:34:57Z"
    - latency: 1.028327ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:33:57Z"
    - latency: 2.529275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:33:57Z"
kind: List
metadata:
  resourceVersion: ""