Design Issue: Config controller (managed) over config connector CRDs - pros/cons

Raised by the team during the weekly meet
Filling out as we investigate......
https://cloud.google.com/anthos-config-management/docs/concepts/config-controller-overview
https://cloud.google.com/config-connector/docs/overview

config controller vs config connector discussion - we will need pros/cons on managed solution in terms of partial control over the upgrade cycle (the normal - no auto update in prod)
Advantages over config controller over config connector (auto update, gke hardening)
Config connector CRD operators - statuses?

Advised auto update not recommended (canary first before updating the prod cluster)
need to check if upgrade is forced - or the normal case where it is available (but we can skip a version or move to an upgrade time like 3am)

will need the roadmap around config controller changes

see https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/architecture.md#di-37-config-controller-vs-config-connector---managed-vs-crds