What is the replacement for vbr backups on containerized installs for Vertica DB

Currently only vertica restorepoints are supported.. what is the specific vbr feature you are looking for?

I'm trying to create a procedure for backup and restore when installing with vertica-operator (containerized). 
Until 24.1.x the procedure was quite clear. Using vbr, the official tool that is also used for non-containerized installations.
I'm trying to understand what would be the roadmap for this feature b/r. Will vbr be deprecated and RestorePoints take its place?
Will we have the same parity in scenarios covered?

Just grabbing some scenarios from the official documentation for non-containerized:
In the case of vbr backup we have:

### DOCS

Before…

Upgrading Vertica to another release.
Dropping a partition.
Adding, removing, or replacing nodes in the database cluster.

After…

Loading a large volume of data.
Adding, removing, or replacing nodes in the database cluster.
Recovering a cluster from a crash.

If…

The epoch of the latest backup predates the current ancient history mark.

###

Not sure how restorepoints will cover these scenarios.
Most probably won't.

I'm interested mostly in a procedure to backup the database full or partially.
In the case of a worst case scenario, a procedure to restore the database with the cloud stored backup (archive).
Just thinking on (not probably the best example) procedure for posgres with pg_dump -> archive created, for restoring pg_restore from archive dump.

Vbr in my opinion did exactly this, which differently restorepoints seems not to do.
The archive directory is a collection of restore points, right, not specifically different backups like in the case of vbr.

Please open a support case. we can discuss further regarding the restorepoints feature.