azure-service-operator

azure-service-operator copied to clipboard

A user should be able to create a K8s resource of any kind. If that resource already exists, then the resource should be owned by the user, not by the controller. Ownership of a resource implies the owner is responsible for the lifecycle of the resource. For example, an owner of a resource is responsible for deletion of the resource, and if a user brings their own resource, the controller should not delete the Azure resource when the K8s resource is deleted.

Transitively, a resource group should not be deleted if it contains resources which are not owned by the owner of the resource group. These resources need not be represented by K8s resources, but do exist in Azure. This implies that there may need to be a mechanism for a K8s resource to check in Azure for child resources owned by other entities.

See the above linked adoption design.

We need to finish the adoption design and make this possible.

The adoption design mentioned above still covers this, although technically it's doable today with reconcile-policy: skip already.

We're still working on this, we're tracking this through the Adoption PR so closing this