Console
Quick Start Cluster Namespace Application Helm Apps F.A.Q

Onboard Existing Application

Users can add an existing application from the Repository. Even if the application type is unavailable in the Container Platform Application type list, users can still onboard the application. But the Prerequisite is the application that it should be dockerized.

To onboard the existing application user will go to Applications -> On-Board Existing App

A popup window will appear user will need to select the repository type whether it’s personal or Organization 

Once the repository is selected the system will show the list of directories under that repository.

Once the directory is selected it will show the list of available applications

Once the application is selected it will show the branch list. The user will select the branch from which he wants to pull the application

Users will select the language type for the existing application. If a docker file is found user can select as follows:

  • Language type: Golang
  • Application type: Golang

Then the user will click on the next button to proceed.

Here users will input the basic information for the existing applications.

Basic Information
Application Name Users will need to Input an Application name
Team Users will need to select a team from the dropdown list
Application Port A post number is needed to input. The application will run on that port
Metrics Port A port number for the Metric should be input here. Thorough metric port system will collect application metrics.
Health Check Type Users will select the health check type for the application.  If health check is not needed user can select none
Extra Exposed Port List If any extra port need to expose this option can used
Enable External Access URL * (Nginx) It will enable external access URL for the NGinX
Enable Traffic Management If “Enable Traffic Management” selected then the Istio mesh will be activated for service to service internal communication and traffic management
Enable Access Control Users can enable HTTP / TCP. For HTTP users can “Enable Sticky Session” (Expiry time).

After providing all the information the user will click on the Next button to proceed.

In this step the user will choose the environment for the Application. User will select single or multiple environments as follows

Dev, Test, QA, Staging, Pre-Prod, Prod

In this step the user will select the Kubernetes Namespace for each environment and configure the resources.

Once user select the Namespace it will show the following form to input deployment details, Resource Configuration ad Default External access settings

A summary of all details of language, framework, and selected configuration for each environment will be visible. the user can review and then create the application. If any changes are needed, the user may go back and update the details as needed.