Skip to main contentCloud-Native Toolkit

Post-installation configuration

Provides a walk-through of the provisioned environment and the steps to validate it is ready to begin on-boarding developers.

Explore the provisioned resources

IBM Cloud resources

Once the Terraform scripts have finished, you can see the resources that the scripts created in IBM Cloud:

  1. In the IBM Cloud console, open the Resource List
  2. On the Resource List page, filter by your Resource Group by selecting the resource group from the Group dropdown (e.g. appdev-team)
  3. You should see these resources listed under the following sections:
    • Clusters: 1, either Kubernetes or OpenShift
    • Services: depending on the configuration could be quite a few (LogDNA, Sysdig, Activity Tracker, Watson Assistant, Watson Studio, PostgreSQL, MongoDB, etc)
    • Storage: possibly Cloud Object Storage

Cluster resources

Log in to the cluster and look at the console to see the resources that have been provisioned within the cluster.

  1. Access the cluster console

    • In the IBM Cloud console, open the Resource List
    • On the Resource List page, filter by your Resource Group by selecting the resource group from the Group dropdown (e.g. appdev-team)
    • Expand the Clusters section and click on the appropriate cluster
    • Click the button to open the Kubernetes or OpenShift web console

  1. Navigate to the tools namespace/project.
  2. Look at the status of the pods in the cluster. All should be either in running or completed state.
  3. If LogDNA or Sysdig were bound to the cluster then a ibm-observe namespace/project should have been created containing a pod for each node in the cluster

Validate LogDNA

If LogDNA was provisioned and/or bound to the cluster, check that log data is flowing into LogDNA

Validate/complete the SysDig setup

Complete the setup of Sysdig and check the monitoring data is flowing

Validate the Developer Dashboard

Test opening the Developer Dashboard

  1. Log into the cluster from the command-line

  2. Run either or all of the CLI options to load the dashboard

    oc dashboard

Validate the installed tools

  1. Log into the cluster from the command-line
  2. Run the IGC CLI credentials command to list the credentials for the tools
    oc credentials -n tools
  3. Use the url and credentials provided for each tool to validate the provided credentials

Additional configuration

The following post installation setup is required. To get the developers enabled quickly, make sure you have completed at least post installation tasks. The customization is optional and down to development team needs.

Customize the Dashboard configuration

Perform the steps in Configure Dashboard to customize tiles and menu items for the tools that are external to the cluster.

Set up user access

Configure the RBAC rules in the development cluster. This restricts who can change the parts of the cluster where the tools are installed.

  1. Run the RBAC script ./terraform/scripts/rbac.sh found in the ibm-garage-iteration-zero repository

Create a CI namespace/project

  1. Log into the cluster from the command-line
  2. Run the IGC CLI sync command to create the namespace/project
    oc sync {project}

Setup a GitOps repo

  1. Follow the steps to create a GitOps repo.
  2. Follow the steps to add configuration for the CI pipeline, using the namespace created in the previous step.

Test the pipeline

The best way to verify that the tools have been configured properly is to deploy a sample pipeline. Follow the deploy an app steps for one of the starter kits to ensure that all the tools have been configured properly.

Note: Use the project/namespace created in the previous two steps when deploying the app

Edit this page on GitHub