Skip to main content
Version: 4

Deploy the application

You can install Adeptia Connect microservices using Helm Charts. A Helm Chart is a collection of files and templates that describe Kubernetes resources governing the deployment of microservices.

  1. Ensure that you have met the prerequisites for installing the application.

  2. Connect to the Jump Box using Remote Desktop Protocol (RDP). It is required only when you use Jump Box for application deployment

  3. Connect to the Cluster.

  4. **Create a Namespace in the cluster.
    **

    errorYou can use the default (named as default) or an existing Namespace, if you do not want to create a new one. 

    Follow the steps given below to create a Namespace in the cluster wherein you want to deploy the application.

    1. Run the following command to create a Namespace, for example, adeptia-connect-ns in the Kubernetes cluster.

    2. Run the following command to verify if you have access to the created Namespace. 

  5. **Apply RBACs.
    **

    This section explains how to update and apply the Kubernetes RBAC configuration required for the user who will manage the Adeptia Connect deployment. Follow the steps below:

    1. Download the Roles package.​

      1. In the Jump Box or your local machine, create a directory, for example, DownloadedRoles.

      2. Navigate to the directory.

      3. Download the package in the directory you created.
        Windows:

        Linux:

    2. Extract the package.​

      1. Run the following command to extract the package in the directory:
        Windows:

        Linux:

    3. Go to the directory roles.
      Linux: 

    4. Open the values.yaml file (located inside roles directory).
      Linux: Run the following command and then press the i (insert) key on the keyboard:

    5. In the adeptiaConnect section in the values.yaml file, provide the values for the following properties as mentioned in the table below:namespace where you intend to deploy Adeptia Connect.

      Property
      		Description
      		Value
      enabled
      		Setting this to true deploys the Adeptia roles. By default the value is set to false.
      		true or false. 
      namespace
      		The namespace where Adeptia roles will be deployed
      		Name of the namespace
      deploymentUser
      		The user who will deploy the Adeptia roles
      		Username

    6. Save and close the file.
      Linux: Press Esc (Escape) key on the keyboard to exit from edit mode, type :wq, and then press Enter to save and close the file. 

    7. Run the following command to deploy the Adeptia roles.

  6. Download the Adeptia Connect package.  ​

    1. Navigate to your user directory as shown in the example below:

    2. Create a directory, for example DownloadedApplication.

    3. Navigate to the directory you created in the previous step.

    4. Download the package in the directory.
      Windows:
      Linux: 

  7. Extract the package.​

    1. Run the following command to extract the package in the directory:
      Windows:

      Linux:

  8. Configure the values.yaml file located at the adeptia-connect directory in the extracted package.​

    1. Navigate to the adeptia-connect directory.

    2. Open the values.yaml file.
      Linux: Run the following command and then press the i (insert) key on the keyboard: 

    3. Configure the values.yaml variables discussed in the section Configuring the values.yaml parameters.

    4. If you want to deploy the application on Azure Red Hat OpenShift (ARO), update values.yaml with the additional required configuration discussed on this page.

    5. If you want to deploy the application on Amazon EKS, update values.yaml with the additional required configuration discussed on this page.

    6. Save and close the file.
      Linux: Press Esc (Escape) key on the keyboard to exit from edit mode, type :wq, and then press Enter to save and close the file.

  9. Deploy the application.

    1. Go to the directory, for example, DownloadedApplication, where you extracted the Adeptia Connect package.

      InformationThe command cd.. takes you back from adeptia-connect (current directory) to the previous directory (The directory, for example, DownloadedApplication, where you extracted the package).

    2. Add repo.

    3. Deploy the application.

      Success
      • <ch:anchor>In case of redeployment of AC application, you can include --set global.config.redeploy=true in the install command. This skips the execution of databasemigration, migration, cleanup, and static jobs, making the redeployment quicker. Given below is example of install command for redeployment.
        <ch:codesample>
        </ch:codesample></ch:anchor>

      After the successful installation of the application, you will see the following message:

  10. **Verify the application deployment.
    **Run the following command to see if all the microservices' pods are up and running as shown in the following screenshot.

  11. Configure Ingress to route traffic to the application.

    After the application is successfully deployed, configure an Ingress resource to allow the NGINX Ingress Controller to route external traffic to Adeptia Connect.

    The Ingress defines the domain and path through which users access the application and forwards matching requests to the deployed services.

    For details on installing and configuring the NGINX Ingress Controller, refer to Setting up the Nginx Ingress Controller.

  12. Log in to the application.

  13. **Configure the mail server parameters.
    **

    After deploying the application, you must configure the Mail Server Parameters so users can receive invitation emails to set up their accounts. Without this post-deployment configuration, invited users will not get the account-setup email.