apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "70128"
    uid: 5bdda06d-d5a3-4159-9bcc-2a3bf6ef6ae8
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:18:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.215178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:44Z"
    - latency: 914.392µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 1.117726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 1.106125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 916.063µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 1.337347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 1.287356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:44Z"
    - latency: 1.172293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:44Z"
    - latency: 967.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:44Z"
    - latency: 1.310063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "69364"
    uid: 7dddfb68-dec8-4111-a0d1-a81f5dab3152
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:17:44Z"
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.550232ms
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 6.552733ms
      message: 'load-balancer-api-external: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 6.86738ms
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 6.801415ms
      message: 'load-balancer-api-external: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 5.026573ms
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 6.703516ms
      message: 'load-balancer-api-external: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 4.014676ms
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 6.65088ms
      message: 'load-balancer-api-external: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 4.728587ms
      message: 'load-balancer-api-external: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 6.955426ms
      message: 'load-balancer-api-external: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "69363"
    uid: bdbca9f9-e88e-48f9-8e11-f3588f991d3d
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:17:44Z"
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.589964ms
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 6.524161ms
      message: 'load-balancer-api-internal: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 6.901127ms
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 6.737408ms
      message: 'load-balancer-api-internal: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 5.10542ms
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 6.668194ms
      message: 'load-balancer-api-internal: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 4.300335ms
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 6.633082ms
      message: 'load-balancer-api-internal: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 4.716553ms
      message: 'load-balancer-api-internal: tcp connection to ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 6.895098ms
      message: 'load-balancer-api-internal: resolved host name ad2b3a1a5fb8b4d17b13abbdc713320e-06b7bedf124c84e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-133-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "70125"
    uid: fdf7dcbe-f098-4955-8818-db00b9f75a72
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:18:44Z"
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.466317ms
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:44Z"
    - latency: 892.426µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 956.559µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 934.898µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 1.056804ms
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 1.025889ms
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 1.110875ms
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:44Z"
    - latency: 873.403µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:44Z"
    - latency: 988.427µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:44Z"
    - latency: 999.062µs
      message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-134-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "70126"
    uid: 8a7db103-89e6-4f21-a9ed-74a57fad5c47
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:18:44Z"
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.210005ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:44Z"
    - latency: 2.282636ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 2.055741ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 2.248079ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 2.086009ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 2.436942ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 2.292286ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:44Z"
    - latency: 2.286756ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:44Z"
    - latency: 2.420673ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:44Z"
    - latency: 2.308537ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-143-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "70127"
    uid: 2aafb8e4-3d0f-4a87-8cc1-e0998959065e
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:18:44Z"
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42717ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:44Z"
    - latency: 2.569395ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 2.194777ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 2.336167ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 2.200816ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 2.336223ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 1.978255ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:44Z"
    - latency: 2.236875ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:44Z"
    - latency: 2.057392ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:44Z"
    - latency: 2.1386ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:11:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-73-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-73.ec2.internal
      uid: e683849e-575b-4a4e-a39a-fbc002f38da6
    resourceVersion: "69362"
    uid: 2ff8540a-ce54-4397-a0fa-84d3072fd4e0
  spec:
    sourcePod: network-check-source-6f8b768455-pphw5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:17:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.266064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 1.734807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:44Z"
    - latency: 1.007282ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 1.593701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:58:44Z"
    - latency: 1.103762ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 2.040825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:57:44Z"
    - latency: 872.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 1.869545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:56:44Z"
    - latency: 1.721007ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:44Z"
    - latency: 1.83652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:55:44Z"
kind: List
metadata:
  resourceVersion: ""