List view
- No due date
- No due date
- No due date
With Heighliner, our aim is to build a system which allows for extreme high available services (using multi-cloud/multi-region clusters etc.). This also means that we need to incorporate unavailability from our Heighliner tool itself. This leads to us having to provide a decoupled way of deploying, but we want to support this through different mediums.
No due dateThe first workload we need to work on is creating our CRDs. This is mostly highlined in the [Heighliner: Kubernetes Deployment Components](https://docs.google.com/document/d/1XSJ3-JL0Hg8zJ56V_kQ49PrEAQh87V4Mn4Ewb4sfwQk/edit#) document. These CRDs allow us to act on changes and make sure the cluster is in the state we want it to be. They should allow us to define a new microservice and have that appear in our kubernetes cluster. This first step does not think about “how will we deploy this” just yet (we’ll keep it in our minds for architectural reason of course).
No due date- No due date
- No due date
- No due date
- No due date
- No due date