Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Before You Install CN2 Pipelines

SUMMARY The following procedures will help you obtain some prerequisites and some values used to fill the values.yaml file for the CN2 Pipelines Helm chart.

Install Helm

Before installing the CN2 Pipelines chart, you need to install Helm 3 in the management cluster. Helm helps you manage Kubernetes applications. Helm charts help you define, install, and upgrade even the most complex Kubernetes application.

Run the following command to download and install the latest version of Helm 3:

Verify Kubeconfig

Before creating the kubeconfig file as base64, verify kubeconfig works from the management cluster.

  1. Copy the kubeconfig file from CN2 to the management cluster. You can do this with a copy and paste.
  2. Run the following command to view the nodes on the CN2 cluster:
  3. Run the following command to view the all the pods on the CN2 cluster:

CN2 Cluster Configuration

CN2 cluster configuration performs the following actions in the CN2 cluster:

  • Creates CN2 Pipelines namespace if namespace does not exist already.

  • Creates a service account named cn2pipelines.

  • Applies the cluster role and role bindings.

Based on the above items, CN2 Pipelines creates a dynamic bearer token to communicate with the CN2 cluster immediately during the provisioning of CN2 Pipelines with Argo CD.

Mountpath for CN2 Cluster Configuration

Place the CN2 cluster configuration with the name config in the mountpath specified in the values.yaml.

For example:

Create a Personal Access Token for GitLab

To create a personal access token, use the following procedure from GitLab:

  1. Select Edit profile.
  2. In the left pane, select Access Tokens.
  3. Enter a name and (optional) expiration date for the token.
    Default expiration is 30 days.
  4. Select the desired scopes.
    See GitLab Personal Access Token Scopes.
  5. Select Create personal access token.
  6. Save the personal access token somewhere safe. After you leave the page, you no longer have access to the token.
    For more information, see GitLab Personal Access Token.

Mountpath and Profiles

You need to put the mountpath in a mountpath folder, then create your profiles in the mountpath folder. For example, if your mountpath is /opt/cn2_workflows as defined in the values.yaml, you will create a folder named /opt/cn2_workflows.

Create a Sample ConfigMap in Git Server Folder

You need to create a sample ConfigMap before installing the CN2 Pipelines. Create and add the sample ConfigMap to the CN2 network configuration folder identified in your GitLab server branch. The same branch and folder also needs to be added in the values.yaml. This ConfigMap gets applied by Argo CD as part of the CN2 Pipelines installation.

  1. Run the following command to create a ConfigMap with the filename cn2configmap:

    Output:

  2. Commit the ConfigMap file to the CN2 configuration folder identified in your Git server branch.

Update /etc/hosts for an OpenShift Deployment

On the CN2 cluster, check the ingress components.

Verify that /etc/hosts contains entries from the OpenShift cluster. For example: