Create Direct Controller Skill

Migrating to a direct controller safely involves keeping the existing Terraform or DCL controller as the default while adding the direct controller to the supported list, enabling side-by-side verification without breaking reconciliation.

A direct controller is a reconciliation mechanism added to a Config Connector resource's supported list. It runs alongside existing Terraform or DCL controllers to verify behavior through computed diffs before becoming the default.

To run golden e2e tests for a direct controller migration, modify tests/e2e/unified_test.go to force direct-side execution for your selected fixture kinds. This computes diffs to verify behavior against the older controller.

Yes, adding a direct controller requires updating pkg/controller/resourceconfig/static_config.go to include k8s.ReconcilerTypeDirect. This defines the DefaultController and SupportedControllers for your target GVK.

Yes, you can verify direct controller behavior without removing the Terraform controller. Keep Terraform as the default and enable golden e2e testing to compute and check diffs between both controllers side-by-side.

The limitation of incremental direct controller rollout is that you must start with a focused set of resource kinds and expand coverage only once behavior matches expectations. It requires strict side-by-side verification to avoid confusing diffs.