Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Feature inquiry: replication #84

Open
BlaineEXE opened this issue Jul 25, 2024 · 2 comments
Open

Feature inquiry: replication #84

BlaineEXE opened this issue Jul 25, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@BlaineEXE
Copy link
Contributor

We had an upstream user inquire about supporting replication. Currently, COSI KEP doesn't explicitly plan for or against adding a replication API.

Replication seems like a fairly high-level feature that might not be supported by all drivers. In a July 2024 COSI meeting, we decided to simply keep tabs on inquiries about the feature to get an idea for how many users are interested to help us prioritize discussions moving forward.

For now, users are encouraged to use 3rd party replication features like rclone or driver-based replication.

Inquiries:

  • Karanjot Singh (CERN, Ceph S3 driver)
@BlaineEXE BlaineEXE converted this from a draft issue Jul 25, 2024
shanduur pushed a commit to shanduur/container-object-storage-interface-api that referenced this issue Aug 2, 2024
…l-manifest-edit

revert accidental image modification in deployment
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 23, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants