Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
77 lines (41 sloc) 3.23 KB


This document describes how to configure a forked Helm Broker bundles repository.


Before you start, install:

  • Kyma in version v0.4.1 or later
  • kubectl in version v1.10.0 or later
  • svcat CLI in version v1.10.0 or later


Follow these steps to configure your own bundles repository and to complete this Getting Started guide.

Create a fork and enable Travis CI with the GitHub repository

  1. Fork the bundle repository.

  2. Go to the GitHub page.

  3. In your GitHub profile account, choose the Settings tab. In the left sidebar, click Developer settings.

  4. In the left sidebar, click Personal access tokens.

  5. Click Generate new token.

  6. Give your token a descriptive name.

  7. Select the public_repo scope of the token.

  8. Click Generate token and copy your personal access token.

  9. Go to Travis CI and sign up with your GitHub account. Accept the Authorization of Travis CI.

  10. Click the Activate button and select your forked bundles repository. Click the Approve & Install button to give Travis CI access to your forked bundle repository.

  11. In the left sidebar, click My Repositories tab and choose your GitHub repository.

  12. Click the More options tab on the right and select Settings.

  13. Go to the Environment Variables section. Set Name as GITHUB_TOKEN. Value is equal to your GitHub personal access token. Click the Add button.

  14. Go to the More options tab and select Trigger build. Select a master branch and click the Trigger custom build button.

Create a bundle

  1. Create your bundle according to the instruction.

  2. Place your bundle into the bundles/ directory.

  3. Along with your bundle directory, update index.yaml which defines the available bundles. Find the instruction on how to create a valid file here.

  4. Commit changes and push them to the master branch.

  5. You can check the build status on Travis CI webpage. The Releasing document describes the tagging and releasing processes.

  6. Configure Helm Broker with the new repository as described here.

Check your Kyma Service Catalog

  1. Go to the Kyma console in your browser.

  2. Choose Environment.

  3. The new bundles are visible in the Catalog section in the left sidebar.

  4. The new bundles should appear. If not then go to the Troubleshooting section.


Check Helm Broker Pod's logs, which can give you a lot of information about the occurred issue. To check the logs, run:

kubectl logs -n kyma-system -l app=core-helm-broker