Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Chart
GitLab Chart
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 471
    • Issues 471
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 21
    • Merge Requests 21
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • charts
  • GitLab ChartGitLab Chart
  • Issues
  • #1586

Closed
Open
Opened Sep 13, 2019 by Willi Eggeling@thewilliContributor

allow for scheduled Registry garbage collection

Summary

Provide a way to setup scheduled gargabe collection for the Docker Registry, at least with a helper just as possible with the Omnibus installation (see below), but preferably automated, without manual intervention required.

Current behavior

  • as the gitlab-ctl command is not available for CNG, there is not straightforward way for Registry gargabe collection.
  • manual gargabe collection is possible, but might lead to data corruption as there is not direct way to put the registry into r/o mode.

Expected behavior

  • automated, scheduled gargabe collection using a Kubernetes-native approach (i.e. CronJob ressources)
  • configurable just as possible for backups

Versions

  • Chart: 5542c0ac
Edited Sep 26, 2019 by Willi Eggeling
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/charts/gitlab#1586