Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-admin CRD compatibility update for 128 #1607

Merged
merged 1 commit into from
Dec 20, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions bundle/manifests/oadp.openshift.io_nonadminrestores.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -537,6 +537,20 @@ spec:
- Created
- Deleting
type: string
queueInfo:
description: |-
queueInfo is used to estimate how many restores are scheduled before the given VeleroRestore in the OADP namespace.
This number is not guaranteed to be accurate, but it should be close. It's inaccurate for cases when
Velero pod is not running or being restarted after Restore object were created.
It counts only VeleroRestores that are still subject to be handled by OADP/Velero.
properties:
estimatedQueuePosition:
description: estimatedQueuePosition is the number of operations
ahead in the queue (0 if not queued)
type: integer
required:
- estimatedQueuePosition
type: object
veleroRestore:
description: VeleroRestore contains information of the related Velero
restore object.
Expand Down
14 changes: 14 additions & 0 deletions config/crd/bases/oadp.openshift.io_nonadminrestores.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -537,6 +537,20 @@ spec:
- Created
- Deleting
type: string
queueInfo:
description: |-
queueInfo is used to estimate how many restores are scheduled before the given VeleroRestore in the OADP namespace.
This number is not guaranteed to be accurate, but it should be close. It's inaccurate for cases when
Velero pod is not running or being restarted after Restore object were created.
It counts only VeleroRestores that are still subject to be handled by OADP/Velero.
properties:
estimatedQueuePosition:
description: estimatedQueuePosition is the number of operations
ahead in the queue (0 if not queued)
type: integer
required:
- estimatedQueuePosition
type: object
veleroRestore:
description: VeleroRestore contains information of the related Velero
restore object.
Expand Down