chengleqi

> > > > need addition note valuesFiles and values can both support multiple Sure. Did you mean [ValuesFrom and Values](https://github.com/fluxcd/helm-controller/blob/a2147639031eb1362360b52c6f596c066270ecc4/api/v2beta1/helmrelease_types.go#L156-L162) in the Deployment additional Settings in the following pic?...

### Deployment Settings  User can set different [ValuesFrom and Values](https://github.com/fluxcd/helm-controller/blob/a2147639031eb1362360b52c6f596c066270ecc4/api/v2beta1/helmrelease_types.go#L156-L162) for each destination (different cluster and different target namespace) with the same [helmtemplate](https://github.com/fluxcd/helm-controller/blob/a2147639031eb1362360b52c6f596c066270ecc4/api/v2beta1/helmrelease_types.go#L238-L283). The devops.kubesphere.io/Application is called "Multi-Clusters Application"...

## General Design ### File Change 1. API ```bash pkg/api/gitops/v1alpha1 ├── application.go (UPDATE) ├── helmtemplate.go (ADD) ├── constants.go ├── groupversion_info.go ├── groupversion_info_test.go ├── image-updater.go ├── image-updater_test.go └── zz_generated.deepcopy.go ``` 2....

> Is that possible to keep using the same version `v1alpha1`? Sure.

@lxm

> We also need to establish a releation between helmrelease and helmchart using `labels` or `annotaions`. > > > when user choose Helm Type and create a new helmrelease the...

### Four use-cases #### 1. User just wants to create a HelmRelease without saving the information (`spec.fluxApp.spec.config.helmRelease.chart`) to a Template. ```yaml apiVersion: gitops.kubesphere.io/v1alpha1 kind: Application metadata: name: chengleqi-test-application-1 namespace: my-devops-projecthmhx2...

赞

/area devops

/test ?