apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "54572"
    uid: ad4a0041-a8c6-44a6-8599-37072ecdaacb
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:21:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.191608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 1.135228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 847.301µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 833.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:39:36Z"
    - latency: 1.097558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:38:36Z"
    - latency: 3.374722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:37:36Z"
    - latency: 906.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:36:36Z"
    - latency: 1.310361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:35:36Z"
    - latency: 1.159373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:34:36Z"
    - latency: 887.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "56155"
    uid: a3598bfa-c4ca-4438-89a2-82a67290c1c9
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:20:36Z"
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.933533ms
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 7.545726ms
      message: 'load-balancer-api-external: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 3.763732ms
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 7.030253ms
      message: 'load-balancer-api-external: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 4.925084ms
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 6.721263ms
      message: 'load-balancer-api-external: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 4.954835ms
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 7.657556ms
      message: 'load-balancer-api-external: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 5.754893ms
      message: 'load-balancer-api-external: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 8.391199ms
      message: 'load-balancer-api-external: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "56156"
    uid: 75f70010-2bda-4511-8940-aa250d9d3301
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:20:36Z"
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.062784ms
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 7.632877ms
      message: 'load-balancer-api-internal: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 4.974874ms
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 7.018211ms
      message: 'load-balancer-api-internal: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 4.867434ms
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 6.770855ms
      message: 'load-balancer-api-internal: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 5.694599ms
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 7.742077ms
      message: 'load-balancer-api-internal: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 5.80007ms
      message: 'load-balancer-api-internal: tcp connection to ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 8.497854ms
      message: 'load-balancer-api-internal: resolved host name ac1ac9dd1310a410ebd4a1b1e4d18ca0-bd69f1afbf0501d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-128-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "54570"
    uid: abd81b75-c65c-4335-8c2e-33a5af54c36c
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:21:36Z"
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.010746ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 2.200474ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 1.956531ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 1.944362ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:39:36Z"
    - latency: 2.004029ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:38:36Z"
    - latency: 3.840388ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:37:36Z"
    - latency: 1.710088ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:36:36Z"
    - latency: 1.83384ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:35:36Z"
    - latency: 1.595211ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:34:36Z"
    - latency: 1.919057ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-132-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "54569"
    uid: 25d94d14-28b7-44cf-b614-c81022128bb7
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:21:36Z"
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.149µs
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 1.264904ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 1.030512ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 831.821µs
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:39:36Z"
    - latency: 1.222532ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:38:36Z"
    - latency: 3.542295ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:37:36Z"
    - latency: 1.204599ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:36:36Z"
    - latency: 1.07383ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:35:36Z"
    - latency: 910.143µs
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:34:36Z"
    - latency: 1.088555ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-network-check-target-ip-10-0-141-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "54571"
    uid: 1fd17a01-bc8d-4db6-8b24-6857ab97b027
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:21:36Z"
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.334322ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 2.354143ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 2.164238ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 1.906518ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:39:36Z"
    - latency: 2.686229ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:38:36Z"
    - latency: 4.880244ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:37:36Z"
    - latency: 2.257492ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:36:36Z"
    - latency: 2.385965ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:35:36Z"
    - latency: 2.114818ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:34:36Z"
    - latency: 2.41799ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:14:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-168-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-168.ec2.internal
      uid: a74ec0e8-6dc9-40c6-ab0f-dfe5e93c05f8
    resourceVersion: "56154"
    uid: 6a680c01-e749-45e0-af96-39a81e3668a3
  spec:
    sourcePod: network-check-source-685456655f-jm9hj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:20:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 2.112682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:44:36Z"
    - latency: 1.205683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 1.994662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:43:36Z"
    - latency: 855.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 2.109848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:42:36Z"
    - latency: 1.200874ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 1.978326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:41:36Z"
    - latency: 874.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:40:36Z"
    - latency: 1.990414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:40:36Z"
kind: List
metadata:
  resourceVersion: ""