<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=561085) </details> <!--IssueSummary end--> <!-- This issue template can be used as a great starting point for feature requests. Learn more about the process: https://handbook.gitlab.com/handbook/product/product-management/#customer-feature-requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve <!-- What is the user problem you are trying to solve with this issue? --> Enabling the [Package Metadata Database](https://docs.gitlab.com/topics/offline/quick_start_guide/#enabling-the-package-metadata-database) for air gapped systemms is complex, due to current methods expecting access to shared storage. This does not operate well in cloud native GitLab installations. ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Implement and document a method for isolating the tasks into Rake and/or isolated Sidekiq queues, so that these can be directly loaded from localized object storage or a filesystem attached to a specific container in a cloud native GitLab installation. While this may remain a manual process, as "sneaker net" shuttling of the Package Metadata DB is mandatory in these environments, we can significantly improve the experience of the GitLab instance Operators, and several other SAST / continuous scanning consumer personas. <details><summary>detailed workaround</summary> 1. Get Package Metadata files off of GCP 1. Add a sufficiently sized PV/PVC to the toolbox pod mounted at `/srv/gitlab/vendor/package_metadata` 1. Copy the licenses and advisories folders into the PVC (`kubectl cp` or similar) 1. Run the following on the toolbox pod (this is out of Duo): 1. `gitlab-rails runner "lease = Gitlab::ExclusiveLease.new('package_metadata_licenses_sync', timeout: 360); lease.try_obtain && PackageMetadata::SyncService.execute(data_type: 'licenses', lease: lease) && lease.cancel"` 1. `gitlab-rails runner "lease = Gitlab::ExclusiveLease.new('package_metadata_advisories_sync', timeout: 360); lease.try_obtain && PackageMetadata::SyncService.execute(data_type: 'advisories', lease: lease) && lease.cancel"` Note: Based on [this cod](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/services/package_metadata/sync_service.rb#L78)e & [this code](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/models/package_metadata/sync_configuration.rb#L109), it appears `PackageMetadata::SyncService.execute` will use the local files before going to GCP. </details> ### Intended users * [Sidney (Systems Administrator)](https://handbook.gitlab.com/handbook/product/personas/#sidney-systems-administrator) * [Ingrid (Infrastructure Operator)](https://handbook.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) * [Isaac (Infrastructure Security Engineer)](https://handbook.gitlab.com/handbook/product/personas/#isaac-infrastructure-security-engineer) * [Alex (Security Operations Engineer)](https://handbook.gitlab.com/handbook/product/personas/#alex-security-operations-engineer) * [Amy (Application Security Engineer)](https://handbook.gitlab.com/handbook/product/personas/#amy-application-security-engineer) ### Feature Usage Metrics N/A ### Does this feature require an audit event? <!--- Checkout these docs to know more https://docs.gitlab.com/ee/development/audit_event_guide/#what-are-audit-events https://docs.gitlab.com/administration/compliance/audit_event_reports/ ---> cc @jdiaz-gitl @hacks4oats