-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
5
-
False
-
None
-
False
-
OCPSTRAT-683 - Migrate MAPI to Cluster API for AWS -Phase 1
-
-
-
CLOUD Sprint 262, CLOUD Sprint 265
Background
We don't know what users will be doing with regards to owner references on MachineSets. Presently, the conversion logic rejects any MachineSet that has owner references on it.
We need to determine valid use cases for MachineSets to have owner references (GitOps? ServiceDelivery tooling? Hive?) and discuss what the appropriate path forward for converting owner references is.
They cannot just be copied as owner references are namespace tied.
Steps
- Investigate possible reasons why a MachineSet might have owner references
- Determine how the migration may work for MachineSets that have owner references
- What do we need to provide to users in this case?
- Discuss with the stakeholders about findings/potential solutions
Stakeholders
- <Who is interested in this/where did they request this>
Definition of Done
- A document as a result of the research and a discussion/arch call with the relevant stakeholders (internal teams wrapping MAPI)
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>