Create Project (Helm Chart Deployment)

Users can create a project that deploys 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.

1. Click the Create Project button on the Main page. You will be taken to the Create Project page.

Enter basic information

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

To enter the basic information, follow the steps below.

1. On the Project Creation page, select the App. Template Utilization option of the Project Configuration Method item.
2. For the deployment target field, select Kubernetes.
3. After entering additional content, click the Start button.

   Item	Explanation
   Project name	Please enter the project name.
   Project ID	Please enter the project ID.
   Project configuration method	Select a project configuration method Use App template: select a pre‑provided App template. Manual configuration: configure without an App template.
   deployment target	Select 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): Package the application as a Docker image and deploy it to a VM server. N/A: Choose this when you do not deploy the build output.
   K8S cluster	Select the target cluster for deployment DevOps Console Only clusters that the user has access rights to can be selected among the K8S clusters.
   namespace	Select the target namespace for deployment Only namespaces that the user has access rights to, among the clusters retrieved from the K8S cluster, can be selected.

   Table. Project creation basic information entry items

App. Select Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Configure code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure Code Quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure Image Repository

Users can configure a repository to store the built container images through the image repository configuration step.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the image repository, follow these steps.

1. In the Image Repository item, select the Repository Type.
2. Create new repository / Use existing repository select, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type 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 formed with the project group name/project name.
   Authentication information	Enter your credentials.

   Table. Project Creation Image Repository Settings

Configure the deployment target environment

Users can deploy by directly configuring via Helm charts.

Helm release name and Helm chart when selected, the Helm chart installation options and the default Values.yaml entries included in the chart are displayed.

Available Helm charts are associated with the App template. You can edit or delete them through Manage supported Helm charts.

To set the deployment target environment, follow these steps.

1. In the Deployment target field, select Configure directly via Helm chart.
2. Please enter the Helm release name.
3. Click the Search button to select the Helm chart to use.
4. After editing Values.yaml, click the Validation Check button.
5. When the Next button is enabled, click the Next button.

   Item	Explanation
   deployment target	Please select the deployment target.
   Helm release name	Enter the name of the Helm release to create. The name must be unique within the namespace of the target cluster.
   Helm chart	Select a Helm chart. When a Helm chart is selected, detailed information about the chosen chart is displayed below
   K8S information	Shows the information of the Kubernetes cluster required for configuring Value.yaml.
   Values. yaml	Edit the contents of Values.yaml. values.yaml file to be used when installing the Helm chart.

   Table. Project creation deployment target environment configuration items

Setting up the build pipeline

Users can configure pipelines that build and deploy applications.

You can view each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. Build Pipeline screen branches based on IDP integration status.
   • For IDP-integrated Jenkins, click the User Check button to perform User Registration Confirmation.
   • For Jenkins not integrated with IDP, enter the authentication information and click the Connection Test button.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
   Category	Select the development/operation distinction. The permissions for the pipeline vary according to the development/operation distinction. Refer to Table. Role-based permissions within the project (1) for role-based permissions.
   URL	Select Jenkins to configure the pipeline, then enter the job name. The Jenkins instances available to the user are displayed.
   Build Agent	Select the agent to be used for pipeline builds. For information about the agent, please refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   User information	IDP Integrated Jenkins Click the User Check button to verify user registration. If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to proceed with User Sign‑Up or Initial Jenkins Login. IDP Non‑Integrated Jenkins Enter the authentication information and click the Connection Test button.
   Set environment variables	Set the environment variables to be registered in the Jenkins pipeline.
   Image Tag Pattern	Select the tag assignment method for the container image.
   Deploy Strategy	Select the deployment method for the container image.
   Recipient of deployment results	Select the user who will receive the results after the build pipeline completes.

   Table. Project creation build pipeline configuration items

Configure Custom Settings

The user can specify and modify the path of the Dockerfile file used for the build.

Additionally, you can view the final script generated based on the information configured in 빌드 파이프라인 설정하기 and also edit it.

Dockerfile, follow these steps to configure the pipeline script.

1. After entering information on the Custom settings page, click the Connection Test button.
2. Click the Next button when the Next button is enabled.

   Item	Explanation
   Dockerfile configuration	Create New Dockerfile or Use Existing Dockerfile. Please select. «Use Existing Dockerfile is only selectable after choosing the Environment Only App template and, in 코드 저장소 설정하기, selecting Use Existing Repository.
   Dockerfile path	Specify the Dockerfile file path in the source code.
   Branch name	The branch name is automatically registered when you set it in Code Repository Configuration.
   Dockerfile	Check and modify the contents of the Dockerfile.
   pipeline script	Check and modify the pipeline script.

   Table. Project Creation Custom Settings Items

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.