Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #36175
Closed
Open
Issue created Nov 12, 2019 by Dmitry Chepurovskiy@dm3ch

Stop requiring gitaly storage with name "default"

Problem to solve

Currently in my installation i have got multiple storages with gitaly[1-n] names that have similar configurations and they are located on VMs named same way. But suddenly I need forced to create gitaly named default cause it's currently required.

Actually I don't understand why default storage is required.

Intended users

Selfhosted gitlab admins

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

Gitalies naming is fully controlled by user

What is the type of buyer?

Links / references

Assignee
Assign to
Time tracking