Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
S
system-charts
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Rancher商店
  • system-charts
  • Repository

Switch branch/tag
  • system-charts
  • charts
  • harbor
  • v1.7.5-rancher1
  • templates
  • registry
  • registry-dpl.yaml
Find file
BlameHistoryPermalink
  • gitlawr's avatar
    Set maxUnavailable to 1 for registry deployment · dd0ab35d
    gitlawr authored Jun 06, 2019
    Problem:
    Registry pod stuck in AttchVolumeFailed status on upgrade. Deadlock happens where the new pod waits the old pod to dettach the volume, and the old one waits for the new one to be ready.
    
    Solution:
    Set maxUnavailable to 1, so that the old pod can be released before the new pod is ready.
    dd0ab35d
registry-dpl.yaml 5.53 KB
EditWeb IDE
×

Replace registry-dpl.yaml

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.