-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
Our OSSM/Maistra API (ie our custom labels and CRDs) is growing with every release, but we don't have a central location for it yet. To avoid circular dependencies between operator and control plane, we're currently keeping multiple copies of the types.go in multiple repositories, incl. codegen.
We should create a maistra/api repository that can be imported by both the operator and the control plane. We can then also have proper documentation generated from docstrings in that repository, which we can point people at as an API reference.
Acceptance Criteria:
- all CRDs and labels are defined in maistra/api repo
- CRD codegen happens in maistra/api
- all other repositories import from maistra/api
- documentation is generated from docstrings
- is related to
-
MAISTRA-2239 Federation CRDs for easier configuration
- Closed
-
MAISTRA-2331 Port maistra/istio-operator to use maistra/api
- New
-
MAISTRA-2330 Port maistra/istio to use maistra/api
- Closed
-
MAISTRA-2332 api: Fix issue with SMCP CRD
- Closed
-
MAISTRA-2346 Create automation for maistra/api
- Closed
-
MAISTRA-2399 Move doc generation from operator to api repo
- Closed