[FOLIO-2183] integrate backend-module pipeline into Jenkins Created: 22/Jul/19 Updated: 03/Jun/20 Resolved: 31/Jul/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | CP: sprint 69, CP: sprint 68 | ||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
Follow up to
This role needs to be integrated into the FOLIO Jenkins pipeline that build the Docker image, as a configurable step. The following open issues listed on
|
| Comments |
| Comment by Ian Hardy [ 29/Jul/19 ] |
|
Notes on portability: Interacting with the kubernetes api is different inside and outside the cluster. If the container that runs kubectl is outside the cluster, we can use a normal kubernetes account to authorize the commands. If the container is inside the cluster, auth variables are automatically overriden and a service account is used. If you do not create/specify a service account the "default" account is used. getting the kubernetes api from a pod: https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-api-from-a-pod |