This repository was archived by the owner on Apr 30, 2020. It is now read-only.
This repository was archived by the owner on Apr 30, 2020. It is now read-only.
CRD Design #3
Description
Describe the feature you'd like to have.
We need to have a well-thought out design for our custom resources so that the project's capabilities can grow over time while minimizing the need for breaking changes to the CRs.
What is the value to the end user? (why is it a priority?)
Avoiding breaking changes will allow the end user to more easily upgrade their system, and it will also permit implementers to build out the system without significant rework of kube-based state.
How will we know we have a good solution? (acceptance criteria)
- The proposed CRD design will take into account all the "modes" of operation (external, manual, and automatic)
- It should account for other functionality such as Day 2 operations
- It should adhere to the Kubernetes API conventions
Additional context
Child of #6