Versions Compared

Old Version 5

changes.mady.by.user Former user

Saved on

compared with

New Version 6

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Auitabs
directionhorizontal
Auitabspage
titleKubernetes

Before you begin

This document assumes that you have completed the instructions in the following guides.

If the above requirements are met let's start modifying product configuration in a step by step manner

  1. Create a fork of the sample chart source repository.

  2. Create a clone of the forked chart source repository as follows.

    xml

    Replace the <ORGANIZATION_NAME> tag with the name of your GitHub organization.

  3. Copy the necessary content of the Kubernetes-is Helm resources (Pattern 1) into the chart source repository from the parent directory.

  4. Clone Kubernetes Resources for WSO2 Identity Server Git repository.

    xml

  5. Declare a variable to indicate the home directory of the Identity Server pattern-1 Helm chart.

  6. Copy content from the Helm chart into the chart source repository

    xml

  7. Modify the config maps to include your modified configuration values.

    E.g., if you want to modify the <HostName></HostName> in the repository/conf/carbon.xml file in the WSO2 Identity Server product pack (product binary can be downloaded from here), you must perform the following tasks:

    1. Create a ConfigMap yaml file in the repository/conf directory in the WSO2 Identity Server product pack. This ConfigMap file should be created in the is-pattern-1/templates/is directory of the chart source repository

      xml

    2. Create a template that holds the value for hostname in the chart source repository created.

      xml

    3. Copy the carbon.xml file located in /wso2is-5.8.0/repository/conf in the WSO2 Identity Server product pack into cicd-sample-chart-is/is-pattern-1/confs/ directory, and replace the default value for hostname with the {{ HOSTNAME }} template.

      xml

    4. Create volume mounts for the ConfigMap in the existing cicd-sample-chart-is/is-pattern-1/templates/is/identity-server-deployment.yaml file in the chart source repository.

      xml

    5. Change the chart data in the sample values file used in the  to use a custom chart.

      Need to change customChart and repo fields with the values shown

      xml

  8. Upgrade the Helm chart with the command below, providing the modified sample values file.

    xml

    <RELEASE_NAME> should be replaced with the release name provided when the pipeline is installed initially in the 

    This may take approximately 10 minutes.

  9. Restart the Jenkins pod by deleting the existing pod. This will cause the cluster to spawn a new pod for Jenkins.

    xml

    Replace <NAMESPACE> with the namespace in your cluster.

  10. Commit and push the changes in your forked chart source repository to master branch with the following commands

    xml

  11. Stop the manual judgment in any existing environments and watch the deployment of the setup with updated configurations being deployed in the Spinnaker dashboard.

    New deployment being made after adding artifact!

What's Next:

Auitabspage
titleAWS

Before you begin

This document assumes that you have completed the Quick Start Guide.

  1. Create a fork of the sample aws-cicd-is-configurationsrepository. 

  2. Create a clone of the forked artifact source repository. You can use the below command in command line.

xml

Identity Server Configuration sample repository will be cloned into your current working directory. Sample

The sample configuration repository uses puppet to apply product configurations.

Add a new JAR.

  1. Copy the new jar file into “modules/is/files/lib” folder in the sample repository.
  2. Edit init.pp inside “modules/is/manifests” folder to copy the JAR into the product.
xml

Update Management console login credentials 

  1. Go to modules /is/manifests/params.pp in the sample repository.pp
  2. Update the below values to change the login credentials.
    1. Management Console Login Credentials

$admin_username

$admin_password

Edit template files

  1. Product configurations are edited using puppet. .erb files for product templates are located inside “modules/is/templates/” folder.
  2. To add /or edit configurations, you need to add /or edit the .erb files.
  3. Refer Product Administration pages for more information.

Update Database Credentials

Once the environments are setup, to change the database credentials follow below steps.

  1. Login to Jenkins console.
  2. Go to Credentials
  3. Click credential with id ‘db_creds’
  4. Click Update on the left menu.
  5. Enter new Username and Password
  6. Click Save.
  7. Go to wso2is-5.8.0 job
  8. Click Build with parameters
  9. Click Build

Once the job is successful, database credentials will be updated. 

Production Best Practices

Refer WSO2 Production best practices guidelines.