[FOLIO-2547] SPIKE: research how to implement folio-snapshot -> folio-snapshot-stable with K8s Created: 30/Mar/20 Updated: 06/Jul/22 Resolved: 06/Jul/22 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | DevOps: sprint 85, DevOps: sprint 86 | ||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||
| Description |
|
Existing promotion cannot be directly mapped to K8s because it relies on EC2 instance labelling and DNS switch over. Propose an alternative for K8s Starting point: autmation/folio-snapshot has a Jenkinsfile whcih is the main configuration for the job (lives in folio-infrastructure) Things invovled
|
| Comments |
| Comment by Jakub Skoczen [ 06/Apr/20 ] |
|
we discussed:
|
| Comment by mark.stacy [ 15/Apr/20 ] |
|
John Malconian Added Google Doc for research on promotion of DNS and completion of task. https://docs.google.com/document/d/1hk0DvvGdRI7VSj_G8eHPcn4kfHNjSE2WVxuev0BDsBk/edit?usp=sharing |
| Comment by mark.stacy [ 19/Apr/20 ] |
|
John Malconian Jakub Skoczen I have added a POC branch(
|
| Comment by Jakub Skoczen [ 20/Apr/20 ] |
|
We have discussed during the planning meeting that we will keep the DNS-based promotion for the K8s deployment. The other thing we discussed is how the tenant management for k8s folio-snapshot will look like:
This behavior differs from the existing snapshot build – where the env is erased when new build is attempted. |
| Comment by Jakub Skoczen [ 06/May/20 ] |
|
John Malconian Zak Burke Cate Boerema BLOCKED until we decide on the future of Nightmare-based UI integration tests. |