As a Rancher user, I would like to deploy Harbor as a catalog application in Rancher 2.0
Now we can add https://github.com/goharbor/harbor-helm into Rancher.
We can deploy Harbor in Rancher with one click.





What we need to do to make it better is following:
Submit a PR to https://github.com/rancher/charts to add Harbor as the default applications in Rancher.
Add question.yaml file which is an enhancement from Rancher. It will help Rancher to generate dynamic UI inputs to make the user experience better. So users can just input and select fields instead of config it in YAML.
Here is an example for questions.yaml https://github.com/rancher/charts/blob/master/charts/wordpress/v1.0.5/questions.yml
There is more information you can find via https://rancher.com/docs/rancher/v2.x/en/catalog/custom/

Please feel free to open PR to rancher.
@ywk253100 / @loganhz
Let's work out what configuration options can be put into the questionable list first. Then sync the followup actions.
Personally, as a downstream platform specific requirement, whether we should put question.yml in the repo is questionable...
How many charts have this file in https://github.com/helm/charts ?
No charts have question.yml files in https://github.com/helm/charts as it is a Rancher defined file.
We are going to create a chart in https://github.com/rancher/charts
We are not going to add question.yml file in https://github.com/goharbor/harbor-helm
We will create a new harbor chart with question.yml file in https://github.com/rancher/charts
Based on the discussion seems there's no code change required in this repo.
@loganhz Do you think we need to keep this issue open?
Could you provide the list of important fields which we can add into Rancher question.yml file, please?
If Harbor chart is deployed in the K8S cluster which enables ingress controller and dynamic volume provision already, the only values that users need to configure are as follows:
expose.ingress.hosts.core, expose.ingress.hosts.notary and externalURL.
thanks. We will work it on Rancher
Most helpful comment
@ywk253100 / @loganhz
Let's work out what configuration options can be put into the questionable list first. Then sync the followup actions.