Use separate api groups for our TPRs
tamalsaha opened this issue · 0 comments
tamalsaha commented
Currently we put all our TPRs under one api group appscode.com. The result of this is all the api types must live under this one unified repo. This creates coupling among unrelated components. This causes problem with dependency management. So, we should use separate api groups for each of our TPR groups. Here is the proposal:
- Voyager: networking.appscode.com
- Searchlight: monitoring.appscode.com
- Restik: storage.appscode.com
- Kubed: cluster.appscode.com
Plan:
- Voyager has external users. So, we can't make breaking changes. We will update this when we add support for new TPR to be introduced in Kubernetes 1.7.0
- Update Searchlight to move the TPRs (breaking change)
- Update Restik to make the breaking change
- Kubed's data currently comes from our api server. We want to transform this into a TPR.