Initiative Overview

During the work on a document to describe how to rotate password in a RHOSO deployment, we found out that a lot of steps were required for the octavia-operator, and that this process could be improved.

Goals

• Analyze potential issues or improvements when rotating password in octavia-operator (in a Spike)
• Define the next steps (tasks) based on the spike (could be: add a mechanism to stop the octavia-health-manager pods, force the restart of the pods when a secret is modified, etc..)
• This work would make it easier for customer to change secrets in octavia in future releases.

Done - Acceptance Criteria

Spike is completed, it can lead to multiple Jira bugs or Features if needed