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
  • PendingReleaseNotes.md
Find file BlameHistoryPermalink
  • travisn's avatar
    ceph: delay starting the system daemons until a cluster is created · c6c4a9b4
    travisn authored Jun 17, 2019
    
    
    When the operator first starts, the only operation needed
    is to watch for new cephcluster crds to be created and
    start the discovery to find available devices. The flexvolume
    agent, the csi driver, and the volume provisioning can all be delayed
    starting until the first cluster is created.
    Signed-off-by: default avatartravisn <tnielsen@redhat.com>
    c6c4a9b4

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