When running helm, the "release name" is hard-coded. It should be set dynamically.

entrypoint.sh should use the kubectl command instead of oc.

When tiller is not installed the entrypoint will call helm template without an explicit --namespace.
If helm templates will use the target namespace the deployment will fail because helm automatically picks the namespace from the current context.

OKD 3.11 Service Catalog backed by ASB configured with the following Strimzi Helm registry adapter:

- type: helm
  name: helmstrimzi
  url: "http://strimzi.io/charts/"
  runner: "docker.io/automationbroker/helm-runner:latest"
  white_list: [.*]

cannot successfully Provision strimzi-kafka-operator 0.8.2 because the following Strimzi Helm registry adapter's index.yaml entry urls property has "-helm-chart" included in its artifact name:

urls:
- https://github.com/strimzi/strimzi-kafka-operator/releases/download/0.8.2/strimzi-kafka-operator-helm-chart-0.8.2.tgz

Helm-bundle-base currently assumes that the index.yaml entry urls property artifact name is strictly composed of: entry-name + '-' + version + '.tgz', which in this case would be "strimzi-kafka-operator-0.8.2.tgz" with no extra "-helm-chart" embedded therein.

There should be a better way of installing helm than having a copy of the binary sitting in this repo.

Helm charts can have one or more templates for testing purposes. This is documented here:

https://docs.helm.sh/developing_charts/#chart-tests

The helm template command will render all templates, including any related to testing. So when the service bundle provisions, it ends up creating those resources.

This image should have a way to exclude test-related resources from provision and deprovision.

One possibility is to just identify any pod definitions that have the annotation helm.sh/hooks: test-success or helm.sh/hooks: test-failure and filter them out of the manifest.