-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Hub to take over "unmanaged resources" in member cluster #360
Comments
I was messing around with a similar thing, where I had existing namespaces and tried to get them into the fleet, Getting the appliedwork object on the member cluster has a uid which you can add to existing resources for the ownerReferences... Sample appliedwork from
Then I updated my namespace with the following ownerReferences metadata add last-applied-configuration annotation:
After a minute or two I was getting proper values for things from the Fleet hub... I hope that can help with your use case! |
Thanks for the suggestion, this is on our road map. |
This feature has been done in our latest release v0.10.3. If the existing resource on the member has no owner reference, appliedWork will be owner. |
There is a use case where namespaces have been created and workloads have been deployed to a cluster. Then this cluster joins the multicluster. In this case, we need to create namespace, namespace scoped resources and CRPs in the Hub. However, when work object is pulled by the work controller in the member cluster, the owner reference check fails in the function isManifestManagedByWork(). We want the work controller to treat this case as Hub taking over previously "unmanaged resources". The work controller shall create appliedWork for this resource and updated CRP status as in the case of successful creation of a new resource (propagated down from Hub) in the member cluster..
The text was updated successfully, but these errors were encountered: