[FOLIO-2554] Deploy edge modules on K8s Created: 06/Apr/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: devops-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-2496 Migrate folio-snapshot reference buil... Closed
blocks FOLIO-2521 Migrate PR builds for platform-comple... Closed
blocks FOLIO-2587 Migrate folio-snapshot-stable referen... Closed
Relates
relates to FOLIO-2547 SPIKE: research how to implement foli... Closed
relates to FOLIO-2560 unify deployment of edge modules betw... Closed
Sprint: DevOps: sprint 86, DevOps: sprint 87, DevOps: sprint 88
Story Points: 1
Development Team: FOLIO DevOps

 Description   
  • consider uinfying the mechanism to deploy edge (and other extras modules) with how the deployment is done in the "release" branch and PR previews (through install-extras.json)
  • the naive approach for providing tenant configuration to the edge module may no longer be sufficient for the shared cluster deployments

The idea is to extend the "module-kubernetes" role part for folio-ansible role to support deployment of edge modules.

There is a role that does if for current folio-snapshot called "edge-module" and "edge-nignx".

  • provide tenant configuration (see above)
  • configure the ingress for nginx for the edge modules


 Comments   
Comment by mark.stacy [ 19/Apr/20 ]

Jakub Skoczen I ran out of time and could not get this task completed. Did initial investigation but was unable to move forward with POC.

Generated at Thu Feb 08 23:21:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.