Di Xu

> You mean handleHelmRelease will only be executed by helmrelease-controller in the next round ? `handleHelmRelease` will be executed by deployer in `clusternet-agent` / `clusternet-hub`. This depends on the cluster...

@wl-chen Would you please share some updates on this issue? Thanks.

> But persistent access to apiserver error, i don't know this will affect cluster performance. Please giver me some advice to avoid the error. Thank you in advance. @Charlottell Yeah,...

> Prevent users from deleting intermediate resources created by clusternet IMO this is feasible by granting appropriate RBAC rules.

> the HelmRelease and Description resources were recreated How come? In Clusternet controllers, these objects will not be recreated, but only be updated or deleted.

> What kind of scene can trigger the controller to delete all Descriptions? When a `Subscription` gets deleted, all the `Descriptions` referring the `Subscription` will be deleted in cascading.

@zjzhangkui Please check whether `ServiceExport` exists in child clusters. Also please check the logs of `clusternet-agent` and find out some suspicious error traces. cc @lmxia Please take a look. Thanks.

This is a known issue that `clusternet-hub` will pick out preferred version or highest semantic version. In Kubernetes v1.22, `autoscaling/v1` has the highest priority than `autoscaling/v2beta2`.

@hangz1995 Yes, it is on our plan. Hopefully that will be available in the coming two releases. Any interests to help integrate this feature?

@xjbdjay Please refer to https://github.com/clusternet/clusternet/blob/main/deploy/templates/helm-chart-private-repo.yaml and https://clusternet.io/docs/user-guide/install-helm-chart-private-registry/.