Deprecate backup upload support for openstack and rackspace
For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features
Deprecation Summary
Uploading backups to remote(cloud) storage relied on third-party gems to automatically upload to Openstack and Rackspace storage. These third-party gems are no longer actively maintained and have not been tested or updated for the latest stable version of Ruby (version 3). Ruby 2 is reached end of support on the 31st of March 2023. Therefore, GitLab will be switching to Ruby 3 in version 15.10. We are deprecating backup upload support for Openstack Swift and Rackspace APIs in 15.10. Customers that are using these providers have the following options:
- Openstack - Change their configuration to use the S3 API instead of Swift.
- Rackspace - Switch to a different provider or manually upload the backup file once the backup task is complete.
Breaking Change
Yes. Customers that upload to openstack can switch to the S3 APIs. Customers who upload backups to rackspace will need to user an alternate provider or manually upload the backup file once the backup task has completed.
Affected Topology
- Self-managed users
Affected Tier
- Free
- Premium
- Ultimate
Checklists
Labels
-
This issue is labeled deprecation, and with the relevant ~devops::
,~group::
, and~Category:
labels. -
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.
Timeline
Please add links to the relevant merge requests.
- As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule:
14.8, 14.9, 14.10, 15.0
–14.8
is the third milestone preceding the major release):-
A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page. -
Documentation has been updated to mark the feature as deprecated.
-
-
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post. - On the major milestone:
-
The deprecated item has been removed. -
If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
-
Mentions
-
Your stage's stable counterparts have been @mentioned
on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.- To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams
- If there is no stable counterpart listed for Support please mention
@gitlab-com/support/managers
- If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
Your GPM has been @mentioned
so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.
Deprecation Milestone
Planned Removal Milestone
Links
- Deprecation notice MR: !108838 (merged)
- Docs note MR: !108849 (merged)
- Removal issue : #387995 (closed)