There is not downstream documentation yet(2020-07-17). So I've get info about "3scale APIaaP CRD's [part 1]" from related THREESCALE-5063 and upstream documentation https://github.com/3scale/3scale-operator/blob/master/doc/operator-capabilities.md

It seems to me that reconcillation is one directional. Example:

1) user creates product via crd

2) user deletes related crd

3) related product is not deleted

I think this is a bug because crd should be one source of truth. I haven't found anything related to this in mentioned documentation.

Note:

There is no downstream documentation yet which should contain at least:

1) crds limitations, unimplemented functionality for product and backend

2) common use-cases, best practices and examples, so user knows when to use crd for defining 3scale objects and what can/should be changed in 3scale instance for having functional product which is ready for production(to be ready to be promoted to production apicast instance and used). Some inspiration can be found in related Epic THREESCALE-3486

Edit:

• Deleting is covered by THREESCALE-5539.
• Operator should synchronize objects created from CRD(product, backend) according related CRD. All changes made by user in 3scale should be changed back, all extra objects(which are supported by CRD) created by user in 3scale should be deleted, all deleted objects(which are supported by CRD) by user should be recreated.