Configure helm repository

Specifies the helm chart repository that is used to push and save the built helm charts of the solutions.

  • Open the helm-repository-controller
  • Use POST method Create a Helm Repository for creating the configuration.

Request parameters

Parameter TYPE Description
helmRepositoryName path parameter (String) The name of the configuration, must be ssob-sdo-helm-push
data body parameter (YAML) The configration values (Body Parameters)

Configuration Parameters (body parameter)

The following table lists the required configurable parameters for the helm repo configuration.

Parameter Description
endpoint The address of the internal s3 service (minio) of the installation, e.g. gitlab-minio-svc.foundation.svc.cluster.local:9000
mode Used storage for the helm charts (possible value s3)
s3.accessKey Access key for the s3 storage (see Getting accessKey and secretAccessKey for minio)
s3.bucketName Used bucket name of the s3 storage (you should ensure that the bucket is already present), e.g. helm-charts-default
s3.disableSsl Specifies if ssl is disabled
s3.region Region of the s3 storage (region in default installation is us-east-1)
s3.secretAccessKey Secret access key for the s3 storage (see Getting accessKey and secretAccessKey for minio)

Example body parameter

endpoint: gitlab-minio-svc.foundation.svc.cluster.local:9000
mode: s3 
s3:  
    accessKey: <ACCESS_KEY>  
    bucketName: helm-charts-default  
    disableSsl: true
    region: us-east-1   
    secretAccessKey: <SECRET_KEY>

Getting accessKey and secretAccessKey for minio

The values for accessKey and secretAccessKey can be found in the minio secret of the namespace where minio was installed, e.g.

For a minio service provided by GitLab the values can be found in a yet exisiting secret, that is located in the namespace where GitLab was installed. By default the secret ends with -minio-secret.

oc -n gitlab get secret gitlab-minio-secret -o jsonpath='{.data.accesskey}'| base64 -d
oc -n gitlab get secret gitlab-minio-secret -o jsonpath='{.data.secretkey}'| base64 -d

The values of the secret have to be base64 decoded.