This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Creating a Project (Helm Chart Deployment)

Note

The user must be enrolled in a project group and tenant to create a project.

For information on how to join a project group and tenant, see Creating a Project Group.

Users can create a project to deploy an application to a specific Kubernetes cluster using App Template, Helm Chart, and Tool Management.

Getting Started with Project Creation

To start creating a project, follow these steps.

Main page, click the Create Project button. This will take you to the Create Project page.

Entering Basic Information

Enter the project’s basic information. The project name and project ID must be unique and cannot be duplicated.

To enter basic information, follow these steps:

Project Creation page, select Project Configuration Method item’s App. Template Utilization.
Select Kubernetes for the Deployment Target item.

Enter additional content and click the Start button.

Item	Description
Project Name	Enter the project name.
Project ID	Enter the project ID.
Project Configuration Method	Select the project configuration method App. Template Utilization: Select a pre-provided App. template. Direct Configuration: Configure directly without an App. template.
Deployment Target	Select the deployment target Kubernetes: Deploy the application to a Kubernetes cluster. Kubernetes(ArgoCD): Deploy the application to a Kubernetes cluster using ArgoCD. VM(Artifact): Deploy the application to a VM server. VM(Docker): Deploy the application to a VM server as a Docker image. N/A: Select if the build result is not deployed.
K8S Cluster	Select the target cluster to deploy `DevOps Console` K8S cluster’s cluster, only clusters with user access rights can be selected.
Namespace	Select the target namespace to deploy K8S cluster’s retrieved cluster, only namespaces with user access rights can be selected.

Table. Project Creation Basic Information Input Items

Selecting App Template

Note

For more information on application templates, see App Template.

Users can select an application template to configure their project.

If you create a project based on an application template with sample source code, you can verify the application to be deployed.

On the other hand, using a template marked as Environment Only configures only the build/deployment environment without sample source code.

If you are using an already configured source code repository to configure your project, select a template marked as Environment Only.

To start choosing an application template, follow these steps:

Application Template screen, enter the template name to select the desired application template card and click it.
When the Next button is activated, click the Next button.

Item	Description
Filter	You can easily find application templates through predefined filters.
Search	You can easily find application templates through search.

Table. Project Creation Application Template Items

Setting Code Repository

The user can set up a repository to manage the source code through the code repository setting step.

Creating a New Repository and Using an Existing Repository activation conditions vary depending on the Application Template and Tool.

Repository Type	App. template with source code + DevOps Console registered tool / DevOps Code	App. template with source code + DevOps Console unregistered tool	App. template without source code (Environment Only) + DevOps Console registered tool / DevOps Code	App. template without source code (Environment Only) + DevOps Console unregistered tool
New Repository Creation	○	X	○	X
Existing Repository Use	X	X	○	○

Table. New Repository Creation and Existing Repository Activation Conditions

Note

Authentication information, once saved, can be used for Using Saved Authentication Information without entering account information, and Connection Test can be performed from then on.

To modify or delete saved authentication information, please refer to Managing Authentication Information.

To set up a code repository, follow these steps:

In the Code Repository section, select the Code Repository type.
Select Create a New Repository or Use an Existing Repository and enter the information.
Enter the Authentication Information and click the Connection Test button.
If the Next button is activated, click the Next button.

Item	Description
Repository Type	Select the code repository to use Registered Tool: You can select and use the types of SCM Repository tools available to the user (`Github`, `Gitlab`, etc.). DevOps Code: Available if you have applied for `DevOps Code` in the Samsung Cloud Platform Console. Unregistered Tool: You can use it by entering the domain of an unregistered tool. The unregistered tool item only appears when the App. template is Environment Only (without source code).
New/Existing Usage	Select whether to Create a New Repository or Use an Existing Repository. The activation status varies depending on specific conditions. For more information, see Table. New Repository Creation and Existing Repository Usage Activation Conditions.
Repository Information	Enter repository information When creating a new repository, the URL is composed of the project group name/project name.
Authentication Information	Enter authentication information If you don’t have an account, you can create one by clicking the Don’t have an account? link and opening the Account Creation Information popup window. After creating a new account, please change your password through the Initial Password Setting link.
(Unregistered Tool) Repository Information	Enter repository information You can use a code repository that is not registered as a tool in `DevOps Console`. You must go through an additional verification process by clicking the URL Check button.

Table. Project Creation Code Repository Setting Items

Setting Code Quality

The user can configure a repository for quality management.

To set up code quality, follow the procedure below.

Code Quality item, select the Repository Type.
Enter Basic Information and Authentication Information, then click the Connection Test button.
When the Next button is activated, click the Next button.

Item	Description
Repository Type	Select the repository to use The types of Code Quality tools available to the user are displayed.
New/Existing/Not Used	Select the repository creation method If you select Create New Repository, you must enter the quality project name/quality project key. If you select Not Created, you can proceed to the next step immediately.
Base URL	Select the `SonarQube` URL.
Quality Project Name	Enter the name of the `SonarQube` project.
Quality Project Key	Enter the key of the `SonarQube` project.
Authentication Information	Enter authentication information You can create a new user or use existing authentication information.

Table. Project Creation Code Quality Setting Items

Setting Image Repository

The user can set up the repository to store the built container image through the image repository setting step.

Note

Authentication information, once saved, can be used for Using Saved Authentication Information without entering account information, and Connection Test can be performed from then on.

To modify or delete saved authentication information, please refer to Managing Authentication Information.

To set up an image repository, follow these steps:

Image Repository section, select the Repository Type.
Select Create New Repository/Use Existing Repository and enter the information.
Enter the Authentication Information and click the Connection Test button.
When the Next button is activated, click the Next button.

Item	Description
Repository Type	Select the type of repository to use The types of Image Registry tools available to the user are displayed.
Repository Information	Select the repository creation method. When creating a new repository, the URL is composed of the project group name/project name.
Authentication Information	Enter the authentication information.

Table. Project Creation Image Repository Setting Items

Setting Release Target Environment

The user can deploy through direct configuration using Helm charts.

When selecting Helm release name and Helm chart, the Helm chart installation items and the default Values.yaml items included in the chart are displayed.

Available Helm charts are linked to App templates. You can modify or delete them through Managing Supported Helm Charts.

To set up the deployment target environment, follow these steps:

Select direct configuration using Helm charts in the deployment target section.
Enter the Helm release name.
Click the Search button to select the Helm chart to use.
Modify the Values.yaml and click the Validation Check button.
Click the Next button when it is activated.

Item	Description
Deployment Target	Select the deployment target.
Helm Release Name	Enter the name of the Helm release to be created. This name must be unique within the namespace of the cluster to be deployed.
Helm Chart	Select the Helm chart. When a Helm chart is selected, detailed information about the selected chart is displayed below.
K8S Information	Displays the information of the Kubernetes cluster required for the Value.yaml configuration.
Values.yaml	Modify the Values.yaml content. This is the `values.yaml` file used when installing the Helm chart.

Table. Project Creation Deployment Target Environment Setting Items

Setting Build Pipeline

Users can configure pipelines for building and deploying applications.

You can check each stage of the pipeline to be configured and change the build job name.

To set up a build pipeline, follow these steps:

Build Pipeline screen branches according to IDP connection.
- For IDP-connected Jenkins, click the User Check button to verify user registration.
- For non-IDP-connected Jenkins, enter authentication information and click the Connection Test button.
When the Next button is activated, click the Next button.

Item	Description
Build/Deploy Pipeline	Displays build/deploy pipeline information. Build/deploy pipeline is displayed based on the information registered in the pipeline template management of the App template.
Classification	Select development/operation classification. Authority for the pipeline varies depending on the development/operation classification. Refer to Table. Authority by Role in Project (1) for role-based authority.
URL	Select `Jenkins` to configure the pipeline and enter the job name. A list of `Jenkins` available to the user will be displayed.
Build Agent	Select the agent to be used for pipeline build. Refer to Agent (Kubernetes) Management and Agent (VM) Management for information on agents.
Build Environment OS	Displays the OS information of the environment where the build agent runs.
User Information	IDP-connected Jenkins Click the User Check button to verify user registration. If not registered as a Jenkins user, a User Registration Guide popup window will open; click the Go to Jenkins link to proceed with User Registration or Initial Jenkins Login. Non-IDP-connected Jenkins Enter authentication information and click the Connection Test button.
Environment Variable Setting	Set environment variables to be registered in the Jenkins pipeline.
Image Tag Pattern	Select the method for assigning tags to container images.
Deploy Strategy	Select the deployment method for container images.
Deployment Result Recipient	Select the user to receive the result after the build pipeline is completed.

Table. Build Pipeline Setting Items for Project Creation

Setting User Definition

Users can specify and modify the path of the Dockerfile file to be used for building.

Additionally, you can check and modify the final script generated based on the information set up in Configuring the Build Pipeline.

To configure Dockerfile and pipeline scripts, follow these steps:

Customize settings page, enter information, and click the Connection Test button.
When the Next button is activated, click the Next button.

Item	Description
Dockerfile Settings	Choose whether to Create a new Dockerfile or Use an existing Dockerfile. Using an existing Dockerfile can only be selected if you choose the `Environment Only` App template and select Use an existing repository in Configuring the Code Repository.
Dockerfile Path	Specify the path of the `Dockerfile` file in the source code.
Branch Name	The branch name is automatically registered when setting up Configuring the Code Repository.
Dockerfile	Check and modify the contents of the `Dockerfile`.
Pipeline Script	Check and modify the pipeline script.

Table. Project Creation Customization Settings

Note

For more information on Jenkins pipeline scripts, refer to the official website.

Completing Project Creation

The user can finally check the project and tool information to be created and start creating the project.

To complete the project creation, follow the procedure below.

Summary Information screen, check the information and click the Complete button.
The Project Creation popup window opens and the project creation proceeds.
After the project creation is complete, click the Confirm button to move to the Project page.

Notice

It cannot be canceled during creation, and if the project is created normally, the Confirm button is activated.