Daniel Jiang
Daniel Jiang
@Vad1mo @wy65701436 Could you check whether there's issue in the settings in the infra?
@Vad1mo Please clarify after the comments by @chlins If there's concern IMO you can update the setting in the deployment of Harbor.
@Vad1mo This seems a valid requirement, would you mind writing up a proposal for this enhancement?
Since the yaml of the resource after restoration looks correct, I think velero's handling it correctly. We'll need to look into this to clarify whether there's any setting at GCP...
When velero restore a PV from native snapshot it's done via static provision and the settings in the storage class won't take effect. I think the gap is how to...
We may use a similar configmap approach or introduce some "restore policy" to make this modification. Leaving it in backlog until we see more use cases.
This is the behavior of the distribution code. Let's double check if this is a known issue.
tentatively move it out of the milestone for now, b/c there may be more complexities. We need a design b/c we need to handle the cases for velero pod, node-agent,...
The imapct is low given we have limitation to the size fo the cache.
Based on the discussion we don't have agreement on the scope and solution for this issue. I'm removing the "candidate" label before "Feature Freeze" of v1.16, and leave it in...