Remote Cluster Condition Enhancement

[stefan-malin-db]

Feature Request

Is your feature request related to a problem? Please describe:
Issue is related to remote cluster option, when we try to create a resource of remote cluster, even if we have chaos mesh instance installed in remote cluster, it still tries to fetch and download public helm chart and we have firewall rules in place in order to prevent public access.

Describe the feature you'd like:
We would like to implement a condition to check if chaos mesh is already installed in a remote cluster, to bypass above step.

Describe alternatives you've considered:
change fetch method from controller implementation to perform above check or implement parameters in order to install chaos mesh from private artifactory.

Teachability, Documentation, Adoption, Migration Strategy:
We plan to use this in our gke clusters, where we need to link services.

[nioshield]

In a private network environment, it may be possible to install using an offline helm chart .
https://github.com/chaos-mesh/chaos-mesh/blob/master/helm/chaos-mesh/values.yaml#L145-L150

[stefan-malin-db]

hello, @nioshield ! Thank you for update, unfornatelly we cannot deploy a private helm chart on gke nodes. We need a method to use a private registry for helm charts.

[stefan-malin-db]

When try to install remote cluster I get:

ERROR remotecluster remotecluster/controller.go:130 fail to list or install remote helm release {"error": "upgrade release chaos-mesh, with chart com-db-olb-chaos-mesh, with values map]: create: failed to create: Secret "sh.helm.release.v1.chaos-mesh.v2" is invalid: data: Too long: must have at most 1048576 bytes", "errorVerbose": "Secret "sh.helm.release.v1.chaos-mesh.v2" is invalid: data: Too long: must have at most 1048576 bytes\ncreate: failed to create\nhelm.sh/helm/v3/pkg/storage/driver.(*Secrets).Create\n\t/tmp/go/pkg/mod/helm.sh/helm/v3@v3.11.1/pkg/storage/driver/secrets.go:164\nhelm.sh/helm/v3/pkg/storage.(*Storage)

How can I fix it?