-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
OADP 1.0.2 release notes #44299
OADP 1.0.2 release notes #44299
Conversation
✅ Deploy Preview for osdocs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
51a3d2b
to
ea85af6
Compare
07d86ad
to
b88557b
Compare
@kaovilai Please add any additional items. |
|
||
.The `kubevirt` Velero plugin is now a default installation option for the OADP operator | ||
|
||
You can now choose the `kubert` Velero plugin as an option when you install the OADP operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can now choose the `kubert` Velero plugin as an option when you install the OADP operator. | |
You can now choose the `kubevirt` Velero plugin as an option when you install the OADP operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we should include compatiblity table
Compatibility
Plugin versions and respective Velero/Kubevirt/CDI versions that are tested to be compatible.
Plugin Version Velero Version Kubevirt Version CDI Version v0.2.0 v1.6.x, v1.7.x v0.48.x >= v1.37.0
|
||
.New Operator update channel lets you pin to a specific 1.0 release | ||
|
||
When you install the OADP Operator, you can now choose `stable-1.0` as your *Update channel* in order to pin your Operator to a specific 1.0 release, for example, 1.0.1 or 1.0.2. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you install the OADP Operator, you can now choose `stable-1.0` as your *Update channel* in order to pin your Operator to a specific 1.0 release, for example, 1.0.1 or 1.0.2. | |
When you install the OADP Operator, you can now choose `stable-1.0` as your *Update channel* in order to pin your Operator to a 1.0 minor release. Patch releases such as 1.0.1 or 1.0.2 cannot be pinned. |
|
||
Known issues:: | ||
|
||
Restore operations using `restic` get stuck with `InProgress` status when an app is deployed with `DeploymentConfig`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we link our workaround?
Known issues:: | ||
|
||
Restore operations using `restic` get stuck with `InProgress` status when an app is deployed with `DeploymentConfig`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
OADP 1.0.2
Resolves https://issues.redhat.com/browse/OADP-365
Adds release notes for OADP version 1.0.2
Preview: https://deploy-preview-44299--osdocs.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-features-plugins.html