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
What happened:
We have lots of existing volume snapshots(> 15,000) in our cluster. Sometimes we created a VolumeSnapshot object , the real snapshotting operation took place after a long time, such more than 5 minutes.
What you expected to happen:
no delay or very short delay How to reproduce it:
This issue needs lots of snapshot objects and not easy to reproduce in test clusters. Anything else we need to know?:
cause by unnecessary k8s cache resync Environment:
Driver version:
Kubernetes version (use kubectl version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
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
Dec 28, 2024
What happened:
We have lots of existing volume snapshots(> 15,000) in our cluster. Sometimes we created a VolumeSnapshot object , the real snapshotting operation took place after a long time, such more than 5 minutes.
What you expected to happen:
no delay or very short delay
How to reproduce it:
This issue needs lots of snapshot objects and not easy to reproduce in test clusters.
Anything else we need to know?:
cause by unnecessary k8s cache resync
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: