Integration - Azure Support for M18
Azure leverages a standard for deploying OSDU services into their environment. The expectation is that Azure documentation and helm charts are written for GCZ specifically, and hosted in the helm-charts-azure repo.
Top priority: Get Kurbernetes Pipelines up and running.
What are helm charts?
- Way of defining resources required to deploy service to Kubernetes
- A set of instructions for building a singular package from a service and deploying that into Kubernetes
Background per CSP:
- Each CSP has different helm charts
- Azure hosts their helm charts in one repo, whereas AWS hosts their helm charts in each service's respective repo for instance
Resources:
- Bryan J Dawson - member of the Architecture SubCommittee - willing to provide guidance on OSDU architecture standards
- Chad Leong - relay any pain points of this process back to Chad so a process can be developed to aid new services into this integration in the future
Acceptance Criteria:
- GCZ Helm Charts created for Azure
- Process documented and relayed to Chad Leong