Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • R Rook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 小 白蛋
  • Rook
  • Repository
Switch branch/tag
  • rook
  • pkg
  • operator
  • ceph
  • cluster
  • osd
  • deviceSet.go
Find file BlameHistoryPermalink
  • Travis Nielsen's avatar
    ceph: allow osd pvc template name set to any value · 20ee66b6
    Travis Nielsen authored Sep 22, 2020
    
    
    The pvc template name has either been require to be empty, or one of the
    expected values such as data and metadata. Those who upgrade from 1.1
    may find that if they changed it to something else, their upgrade will
    fail when not one of these values. If there is only a single template,
    always treat it as the data template.
    Signed-off-by: default avatarTravis Nielsen <tnielsen@redhat.com>
    (cherry picked from commit 2b9e7a53)
    20ee66b6

免费DevSecOps平台,让您的项目体验完整的DevSecOps流程,让项目更安全