Adam

可以换种operator实现的方式：通过将你的crd的增删改查接口注册apiserver 聚合层上 这样crd就不会存在etcd里，而是你自己的数据库里。详见[k8s 文档](https://kubernetes.io/zh-cn/docs/tasks/extend-kubernetes/setup-extension-api-server/#%E5%AE%89%E8%A3%85%E4%B8%80%E4%B8%AA%E6%89%A9%E5%B1%95%E7%9A%84-api-%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%9D%A5%E4%BD%BF%E7%94%A8%E8%81%9A%E5%90%88%E5%B1%82)

/retest

I have offer a PR for it ，please have a look :) @yxxhero

https://github.com/helm/helm/blob/82a2a2e85ccd9f83455b211ac2a7c7c887ffb9bd/pkg/action/action.go#L198-L211 As the annotation shows above，**writeToFile** in the method **renderResources** which used by install & upgrade action should be moved to `template`. that' s just why we cann't filter file...

> helm will delete these resources first, then upgrade resources which have already existed in k8s cluster. During `helm upgrade`, helm will generate `target release` and `original release` , check...

I have opened this PR & issue for three months, Although I will merge the code every time the `main` branch is updated， with more and more conflicts, I can...

I think it's not so robust to create a new registry client here,so I export RegistryClient field in `ChartPathOptions` and use it instead.

could anyone take a look ?

Add new method `GetRegistryClient` to solve this simply

I found code below, it seems we didn't set the field `RegistryClient` which used by cmd/helm/dependency_update.go:66 there is no way to get a ready-made registryClient except creating a new one...