-
Initiative
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
False
-
Not Selected
-
XCMSTRAT-491ARO HCP (P1) - Integrated Development (Renamed from Internal MVP)
-
0% To Do, 0% In Progress, 100% Done
-
0
Unknowns
- How does CS consume versions on startup? For MVP hardcode single version in the DB
Estimation: 9 weeks + 2 weeks holidays
Goal
The purpose of this initiative is to implement the minimal list of changes that would allow deploying and running CS on AKS
Benefit Hypothesis:
The benefit is that we will be able to test Clusters Service in AKS as with the smallest set of changes required, this will allow us to:
- Find issues that may arise from deploying on AKS
- Allow e2e integration with other components such as the RP in a Azure only context
Resources
<Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.>
Responsibilities
- ARO HCP engineering team
- Architecture
Success Criteria
- Clusters Service successfully running in AKS
Results
<Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.>
- depends on
-
XCMSTRAT-531 CS can run in an environment where AMS is not present
- Closed