[Parent Epic] Vendor IAC
Problem Statement
Platform One mandates that all supported Kubernetes distribution contain IAC on repo1. However, there is currently no way to validate that the provided IAC is functioning within the various constraints of P1 and its customers. On the other side of the coin, there is no formal mechanism for Big Bang to validate a deployment against vendor provided IAC and inform customers.
This not only creates confusion amongst current and potential Platform One customers on which distros Big Bang is supported on, but also lacks transparency for vendors looking to submit and validate IAC on repo1.
Ultimately, Big Bang is designed to run without limitation on any CNCF compliant Kubernetes distribution. To validate that claim, we need to be repeatably testing against the various distributions.
Proposal
Build a pluggable CI framework to test vendor IAC and Big Bang deployments. Ensure framework is flexible enough for vendors to provide their IAC within certain P1/BB provided constraints.
- Big Bang to provide a pluggable framework for vendors to test their IAC
- P1 validates that vendor-provided IAC is compatible for each BB release via CI/CD which consumes respective vendor repos in a sandbox environment
- Vendor IAC will be published to this repository
Constraints
- Currently Big Bang can only be tested on AWS and does not have a way forward for other K8s cloud distros (i.e. AKS, GKE, etc.)
- It is the vendor's sole responsibility to ensure IAC is functioning within the constraints of the provided pluggable framework.
- Given the P1 pluggable framework, vendors are responsible for:
- deploying / testing BB in their own environment
- contributing working IAC to the repo1.dso.mil/platform-one/distros
- opening repo1.dso.mil/platform-one/big-bang issues to resolve discrepancies related to the BB product