IBM Cloud Charts Helm Repository

Overview

The IBM/charts repository provides Helm charts for use with IBM Cloud Private.

This repository is organized as follows:

The stable directory contains Helm chart source provided by IBM, while the repo/stable directory contains the packaged Helm chart binaries. To add the stable repo to local repository list run the following command :

helm repo add stable https://raw.githubusercontent.com/IBM/charts/master/repo/stable

The community directory contains Helm chart source provided by the wider community, while the repo/community directory contains the packaged Helm chart binaries. To add the community repo to local repository list run the following command :

helm repo add community https://raw.githubusercontent.com/IBM/charts/master/repo/community

Both the repo/stable and repo/community directories are Helm repositories, and their index.yaml file is built automatically based on the MASTER branch. As of IBM Cloud Private version 3.1.1, both the repo/stable and repo/community repositories are part of the default configuration of IBM Cloud Private, and as such, all charts in those repository will be displayed by default in the IBM Cloud Private catalog.

Getting Started

IBM Cloud Kubernetes Service

If you are new to the IBM Cloud Kubernetes Service platform, information on how to deploy can be found in this tutorial.

IBM Cloud Private

There are a number of ways to start using IBM Cloud Private today, including these offerings:

• IBM Cloud Private Hosted Trial
• A Two-Week Trial on IBM Power Development Cloud
• IBM Cloud Private on AWS Quick Start
• Deploy IBM Cloud Private CE Using Vagrant
• IBM Cloud Private with OpenShift

Configure the kubernetes command line interface for IBM Cloud Private

To access the kubernetes apiserver, you will need an authorization token and the kubectl as the access client. In IBM Cloud Private, authorization tokens can be requested via the dashboard or the REST API.

• Dashboard: Get authorization tokens via Dashboard

• KnowledgeCenter: APIs.

Once you have an authorization token, you can configure kubectl:

export MASTER_IP=10.x.x.x
export CLUSTER_NAME=cloud-private
export AUTH_TOKEN=$(curl -k -u admin:admin https://$MASTER_IP:8443/acs/api/v1/auth/token)

kubectl config set-cluster $CLUSTER_NAME --server=https://$MASTER_IP:8001 --insecure-skip-tls-verify=true
kubectl config set-context $CLUSTER_NAME --cluster=$CLUSTER_NAME
kubectl config set-credentials user --token=$AUTH_TOKEN
kubectl config set-context $CLUSTER_NAME --user=user --namespace=default
kubectl config use-context $CLUSTER_NAME

Then configure your helm command line interface to work with helm.

Copyright IBM Corporation 2019. All Rights Reserved.