[FOLIO-2311] Consider more aggressive cleanup for preview tenants Created: 18/Oct/19 Updated: 03/Jun/20 Resolved: 28/Oct/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Ian Hardy | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 75 |
| Story Points: | 2 |
| Development Team: | Core: Platform |
| Description |
|
Currently, the tenant cleanup process for PR previews in Kubernetes is to check if the corresponding PR is open. If there are multiple builds of one PR, then multiple tenants for that PR will exist until the PR is closed (even though there will only be one stripes bundle available at a time). Consider a more aggressive cleanup approach to only have the latest tenant. Approach is likely to add logic that deletes the tenant if the build number is not the greatest of all builds on that PR. |
| Comments |
| Comment by Ian Hardy [ 25/Oct/19 ] |
|
Added logic to determine the max build number for tenants created on an open pr and delete all tenants where build != max build number for that PR. |
| Comment by Ian Hardy [ 28/Oct/19 ] |
|
tested & pushed changes to folioci/tenant-cleanup:latest container. |