Cleans up policy, placementrule and placementbinding used to replicate the volsync secret (if they exist) does not throw an error if they do not exist.

Convert from schedulingInterval which is in the format of <num><m,h,d> to the format VolSync expects, which is cronspec: https://en.wikipedia.org/wiki/Cron#Overview.

Function to deploy Volsync from ACM to managed cluster via a ManagedClusterAddOn Calling this function requires a clusterrole that can create/update ManagedClusterAddOns Should be called from the Hub.

Should be run from a hub - assumes the source secret exists on the hub cluster and should be propagated to destClusters.

For ReplicationDestination - considered ready when a sync has completed - rsync address should be filled out in the status - latest image should be set properly in the status (at least one sync cycle has completed and we have a snapshot).

Creates a new volsync replication secret on the cluster (should be called on the hub cluster).

ValidateObjectExists indicates whether a kubernetes resource exists in APIServer.

See: https://issues.redhat.com/browse/ACM-1256 https://github.com/stolostron/backlog/issues/21824.

TODO: point to volsync constant once it is available.

Needs to have this name.

Every 10 mins.