apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "48628"
    uid: 244b0ec4-7e81-4402-a5fa-e701c42466de
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:13:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 1.018912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 1.066339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 689.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:31:56Z"
    - latency: 1.168465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:30:56Z"
    - latency: 1.300208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:29:56Z"
    - latency: 1.03383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:28:56Z"
    - latency: 1.113837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:27:56Z"
    - latency: 1.256959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:26:56Z"
    - latency: 1.115956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "50956"
    uid: d5832c6e-6ae8-4251-8bac-c67afad77a0c
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:12:56Z"
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.202374ms
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 8.480302ms
      message: 'load-balancer-api-external: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 5.38879ms
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 8.139939ms
      message: 'load-balancer-api-external: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 5.726327ms
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 8.163836ms
      message: 'load-balancer-api-external: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 4.472677ms
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 8.404577ms
      message: 'load-balancer-api-external: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 5.231763ms
      message: 'load-balancer-api-external: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 7.494486ms
      message: 'load-balancer-api-external: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:32:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "50955"
    uid: f2cf7523-3d79-45da-a9fe-8795609e0e0f
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:12:56Z"
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.170313ms
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 8.429121ms
      message: 'load-balancer-api-internal: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 5.388266ms
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 8.255492ms
      message: 'load-balancer-api-internal: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 5.775241ms
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 8.248919ms
      message: 'load-balancer-api-internal: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 4.48795ms
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 8.50502ms
      message: 'load-balancer-api-internal: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 4.608582ms
      message: 'load-balancer-api-internal: tcp connection to a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 7.645268ms
      message: 'load-balancer-api-internal: resolved host name a1cf215dcfae14978b8f0e8f4f494824-729f91f438b9afae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:32:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-128-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "48626"
    uid: 490f1fae-7c2f-4f62-8f5f-814c3f99c471
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:13:56Z"
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.276116ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 2.012064ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 1.858136ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 2.006146ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:31:56Z"
    - latency: 2.168027ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:30:56Z"
    - latency: 2.185132ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:29:56Z"
    - latency: 2.213824ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:28:56Z"
    - latency: 2.125538ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:27:56Z"
    - latency: 2.071981ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:26:56Z"
    - latency: 2.089586ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-142-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "48624"
    uid: e5d75df9-0b61-4c90-8ca6-0decc957107a
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:13:56Z"
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950672ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 1.932335ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 1.968127ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 1.875723ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:31:56Z"
    - latency: 1.842086ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:30:56Z"
    - latency: 1.781558ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:29:56Z"
    - latency: 1.981557ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:28:56Z"
    - latency: 2.166212ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:27:56Z"
    - latency: 1.777006ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:26:56Z"
    - latency: 1.871106ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-142-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "48625"
    uid: 143081d6-e53c-4b88-b4e7-cc2a97f4c653
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:13:56Z"
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.054µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 808.418µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 736.233µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 1.318007ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:31:56Z"
    - latency: 863.697µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:30:56Z"
    - latency: 828.036µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:29:56Z"
    - latency: 824.125µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:28:56Z"
    - latency: 775.211µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:27:56Z"
    - latency: 818.866µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:26:56Z"
    - latency: 903.422µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: bb2628e6-526f-4773-ae6e-14e45c101a01
    resourceVersion: "50954"
    uid: f2aed3df-e50c-4720-bf62-cf51a0b4edbc
  spec:
    sourcePod: network-check-source-989f8b8dc-t6rld
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:12:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 1.743062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:36:56Z"
    - latency: 1.021022ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 1.770726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:35:56Z"
    - latency: 748.132µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 1.772899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:34:56Z"
    - latency: 868.493µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 1.554301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:33:56Z"
    - latency: 887.463µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:32:56Z"
    - latency: 1.534135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T19:32:56Z"
kind: List
metadata:
  resourceVersion: ""