2019-08-14 Kubernetes Subgroup Meeting notes
Date
Location
Attendees
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
10 min | CI/CD: Standing up a FOLIO system with Kubernetes and Ansible | Role refactoring in folio-ansible (see - FOLIO-2187Getting issue details... STATUS ) allows use of existing code to stand up a FOLIO system. | |
Meeting notes Ian demoed how he is using a bastion container within the cluster to run an Ansible playbook to deploy a backend FOLIO system for a tenant. The playbook uses roles defined in folio-ansible to stand up modules and configure Okapi for the tenant. | |||
5 min | WIP: Standing up EKS with Ansible | ||
Meeting notes Wayne shared some of his current work, using an Ansible playbook to provision an EKS cluster in an AWS region. The goal is to link this work with Ian's to be able to automate standing up FOLIO on EKS and maintain a set of FOLIO installations across regions using Ansible for configuration management. | |||
10 min | Future topics/discussion | Wayne Schneider |
|
Meeting notes Quick update on Okapi/Kubernetes integration: most users have worked around the issues with integrating Okapi discovery with Kubernetes service registration, so - OKAPI-729Getting issue details... STATUS is a lower priority. There is still interest in embedding Kubernetes JSON in LaunchDescriptors ( - OKAPI-736Getting issue details... STATUS ). We are also looking at other ways of describing resource requirements in the ModuleDescriptor, see - FOLIO-2185Getting issue details... STATUS (related to - FOLIO-1729Getting issue details... STATUS ). Subgroup members are asked to look at the list of future topics above and comment on Slack if there are other things that would be interesting to discuss. |
No meeting on 21 August 2019 (many Core: Platform team members at Index Data team meeting).