How do you deploy a helm chart that already exists?
A customer asked: > How do you deploy a helm chart that already exists?
The answer to this question will depend upon how you are deploying your service. ## If you are deploying manually You can follow the steps in [our walkthrough example here](https://github.com/gruntwork-io/helm-kubernetes-services/tree/master/examples/k8s-service-nginx). When you reach the step: ``` helm install -f values.yaml ../../charts/k8s-service ``` you would replace the chart path with your own chart path. ## If you're deploying via Gruntwork modules Our k8s-service helm repository is currently [baked into our k8s-service module](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/services/k8s-service/main.tf#L30-L31). There is currently no way to pass in your own helm chart repository. If you wanted to write a custom module, you could fork this module and update the Gruntwork helm chart repository with your own repository, but note that, as [this issue](https://github.com/gruntwork-io/terraform-aws-service-catalog/issues/50) notes, this is currently sub-optimal as it requires you to maintain your own public domain.