Uploaded image for project: 'Network Hardware Enablement'
  1. Network Hardware Enablement
  2. NHE-369

BF-2 in DPU mode, lifecycle management

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • DPU
    • None
    • BF-2 in DPU mode, lifecycle management
    • True
    • Show
      https://issues.redhat.com/browse/NHE-385
    • False
    • Not Selected
    • To Do
    • 22% To Do, 0% In Progress, 78% Done

      BF-2 reboots and upgrades need to be handled properly in the two-cluster design.

      Flow of dpu lifecycle controller:

      1. Creating deployment with pod that only run sleep
      2. Creating pdb that will block pod draining
      3. In case tenant kubeconfig is not set allow user to remove pdb manually if host is unschedulable.
      4. In case tenant kubeconfig is set and node mapping exists create nodemaintenance cr on tenant cluster
      5. On node uncordon delete NM cr and create pdb as it was

              bnemeth@redhat.com Balazs Nemeth
              bnemeth@redhat.com Balazs Nemeth
              Ying Wang Ying Wang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: