You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use your s5cmd utility along with the kubectl utility to perform backups/restores of object stores provisioned by Rook Ceph in our Kubernetes cluster. The object buckets are represented by Object Bucket Claims and Object Buckets. To implement this, we need to have a container with the s5cmd utility, the kubectl utility, and bash to script the various tasks. Presently, the s5cmd contains a couple of dynamic library references which make this a little more complex:
Would you consider statically linking the s5cmd executable so that it can be more easily copied to a new container and combined with other utilities as descrbed?
The text was updated successfully, but these errors were encountered:
We use your s5cmd utility along with the kubectl utility to perform backups/restores of object stores provisioned by Rook Ceph in our Kubernetes cluster. The object buckets are represented by Object Bucket Claims and Object Buckets. To implement this, we need to have a container with the
s5cmd
utility, thekubectl
utility, andbash
to script the various tasks. Presently, the s5cmd contains a couple of dynamic library references which make this a little more complex:Would you consider statically linking the s5cmd executable so that it can be more easily copied to a new container and combined with other utilities as descrbed?
The text was updated successfully, but these errors were encountered: