The IBM/charts repository provides Helm charts provided for use with IBM Cloud Private.
The repository is organized as follows:
The stable directory contains Helm chart source only provided by IBM, while the repo/stable directory contains the packaged Helm chart binaries.
The community directory contains Helm chart source only provided by the wider community, while the repo/community directory contains the packaged Helm chart binaries.
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.
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_NAMEThen configure your helm command line interface to work with helm.
Copyright IBM Corporation 2019. All Rights Reserved.