apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "18236"
    uid: 773f3107-1773-4f21-8161-66ab6240d5d1
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:13:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:20:57Z"
    - latency: 1.209619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:19:57Z"
    - latency: 1.162514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 1.077522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 1.481259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 1.189728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 1.063178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 967.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:13:57Z"
    - latency: 844.576µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:12:57Z"
    - latency: 1.06718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:11:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "16778"
    uid: 7ca51c67-0273-4ce0-a20c-66b46e296bc8
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:12:57Z"
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.21624ms
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 10.334336ms
      message: 'load-balancer-api-external: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 5.147224ms
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 10.263328ms
      message: 'load-balancer-api-external: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 6.232244ms
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 15.14425ms
      message: 'load-balancer-api-external: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 6.066539ms
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 8.087324ms
      message: 'load-balancer-api-external: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 6.678397ms
      message: 'load-balancer-api-external: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 8.77038ms
      message: 'load-balancer-api-external: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:14:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "16777"
    uid: 87ed9f36-0d15-49be-acb9-c448664d963a
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:12:57Z"
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.228109ms
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 10.242394ms
      message: 'load-balancer-api-internal: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 5.163086ms
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 10.28866ms
      message: 'load-balancer-api-internal: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 6.803465ms
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 14.934493ms
      message: 'load-balancer-api-internal: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 6.055495ms
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 8.175298ms
      message: 'load-balancer-api-internal: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 6.60884ms
      message: 'load-balancer-api-internal: tcp connection to ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 8.88478ms
      message: 'load-balancer-api-internal: resolved host name ad56f6cafa7ed4316ab80d1763f1582c-20320c33a2ae7604.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:14:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-132-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "18234"
    uid: 73bf4147-eadb-42aa-80d6-1b94f1e0cfb1
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:13:57Z"
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.884915ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:20:57Z"
    - latency: 2.495844ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:19:57Z"
    - latency: 2.970815ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 2.251621ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 3.250075ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 1.902269ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 2.10387ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 2.017101ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:13:57Z"
    - latency: 2.454766ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:12:57Z"
    - latency: 1.974774ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:11:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-136-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "18233"
    uid: 428cda56-6b09-4a37-97e6-30dc324b043b
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:13:57Z"
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.726793ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:20:57Z"
    - latency: 965.73µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:19:57Z"
    - latency: 1.254962ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 1.190905ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 1.768172ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 959.165µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 1.058666ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 868.482µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:13:57Z"
    - latency: 711.172µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:12:57Z"
    - latency: 879.748µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:11:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-139-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "18235"
    uid: 4c245f79-f424-4826-92ee-d440c1ce3569
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:13:57Z"
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.4801ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:20:57Z"
    - latency: 2.304903ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:19:57Z"
    - latency: 3.051968ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 3.051654ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 3.169518ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 2.537071ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 2.070677ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 2.642358ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:13:57Z"
    - latency: 2.399342ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:12:57Z"
    - latency: 2.467075ms
      message: 'network-check-target-ip-10-0-139-113: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:11:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T12:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: 534e9d56-7faf-49f5-9360-fa94bf7ad761
    resourceVersion: "16776"
    uid: b00590c9-08a1-4227-89bd-568632d1b35d
  spec:
    sourcePod: network-check-source-7cbc45fddc-2fxjh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T12:12:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.173715ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 2.761071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:18:57Z"
    - latency: 846.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 2.203815ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:17:57Z"
    - latency: 2.295418ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 4.175064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:16:57Z"
    - latency: 885.795µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 1.701506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:15:57Z"
    - latency: 1.167042ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T12:14:57Z"
    - latency: 1.786444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T12:14:57Z"
kind: List
metadata:
  resourceVersion: ""