Is it possible to use the ouster os1 driver with nav2 in galactic as a lifecycle node?

edit

Hello, recently the team I work on has been having issues when running the ros2_ouster driver as a lifecycle node with nav2 after updating from foxy to galactic. In particular, when launching the stack, the bond server will fail to recive a heartbeat from the os1 node, causing it to transition all of nav2 down. If we extend the bond server timeout, then it will run fine until the timeout is hit, where the bond server will error and tear it down. We have no trouble running nav2 in ign gazebo or on the bot without the ouster driver, so it seems to be localised to the ouster driver/lifecycle manager.

Launch file snippit (abbreviated for readablity):

    ...  
    lifecycle_nodes = [
                'ouster_driver','controller_server', 'planner_server', 'recoveries_server',
                'bt_navigator', 'waypoint_follower'
            ]
    ...

return LaunchDescription([
...
Node(
             package='ros2_ouster',
             executable='ouster_driver',
             name='ouster_driver',
             output='screen',
             emulate_tty=True,
             parameters=[configured_params]),
...
Node(package='nav2_lifecycle_manager',
             executable='lifecycle_manager',
             name='lifecycle_manager_navigation',
             output='screen',
             parameters=[{
                 'use_sim_time': use_sim_time
             }, {
                 'autostart': autostart
             }, {
                 'node_names': lifecycle_nodes
             }]),
    ])