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

Return to the regular view of this page.

Create Project (ArgoCD Deployment)

    Note
    • Users must be members of a project group and tenant to be able to create projects.
    • Refer to Create Project Group for how to join a project group and tenant.
    • Deployment via ArgoCD requires that ArgoCD and the Git repository to be used for GitOps deployment be prepared in advance.
    • In the Devops Console, deployment is performed using the pre‑configured ArgoCD and its associated Git information.

    Users can create a project that deploys using App.Template, Tool Management, and ArgoCD.

    Getting Started with Project Creation

    To start creating a project, follow the steps below.

    1. On the Main page, click the Create Project button. You will be taken to the Create Project page.

    Enter basic information

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

    To enter the basic information, follow the steps below.

    1. Enter the project name and project ID.
    2. For the Project Configuration Method item, select App. Template Utilization.
    3. Please select deployment target as Kubernetes(ArgoCD).
    4. Please select the ArgoCD App creation method.
      • Create a new App: When creating a project, create a new ArgoCD application in ArgoCD.
      • Use existing App: Create a project using the existing ArgoCD application.
    5. After completing each input, click the Start button.

    App. Select Template

    Note
    For detailed information about the application template, see App.템플릿.

    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.
      ItemExplanation
      FilterYou can easily find application templates using predefined filters.
      searchYou 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.

    Repository typeApp with source code. Template
    +
    DevOps Console registration tool
    App with source code included. Template
    +
    DevOps Console unregistered tool
    Source code not included (EnvironmentOnly)
    App. Template
    +
    DevOps Console registration tool
    Source code not included (Environment Only)
    App. Template
    +
    DevOps Console unregistered tool
    Create new repositoryXX
    Use existing repositoryXX
    Table. Conditions for creating a new repository and enabling use of existing repository

    Note
    Once authentication information is saved, you can perform a Connection Test without entering account information by using Use Saved Authentication Information thereafter.

    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.
      ItemExplanation
      Repository typeSelect 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 usagePlease select New repository creation or whether to use an existing repository.
      Repository informationEnter repository information
      • When creating a new repository, the URL is formed from the project group name/project name.
      Authentication informationEnter 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.
      ItemExplanation
      Repository typeSelect the repository to use
      • The types of Code Quality tools available to the user are displayed.
      New / Existing / Unused statusSelect 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 URLSelect the SonarQube URL.
      Quality Project NameEnter the name of the SonarQube project.
      Quality Project KeyEnter the Key of the SonarQube project.
      authentication informationEnter 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.

    Note
    Once authentication information is saved, you can perform a Connection Test without entering account information by using Use Saved Authentication Information thereafter.

    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.
      ItemExplanation
      Repository typeSelect the repository type to use
      • The types of Image Registry tools available to the user are displayed.
      Repository informationSelect the repository creation method.
      • When creating a new repository, the URL is formed with the project group name/project name.
      Authentication informationEnter your credentials.
      Table. Project Creation Image Repository Settings

    Configure the deployment target environment

    Note

    To set the deployment target environment, ArgoCD and the Git repository to be used for GitOps deployment must be prepared.
    ArgoCD App creation method The input values vary depending on the selection.

    • Create new App
    • Use existing App

    Create new App

    To create a new ArgoCD application and set the target deployment environment, follow the steps below.

    1. On the Deployment target environment screen, enter the ArgoCD URL and click the Confirm button.
    2. The authentication information entry screen appears.
    3. Enter Authentication information and click the Connection Test button.
    4. The input screen for the new ArgoCD application appears.
    5. Enter ArgoCD application name and ArgoCD project name.
    6. Select the Repository type.
    7. Please select Helm chart.
    8. Information about Helm chart and Helm chart Git repository is displayed.
    9. After editing Values.yaml, click the Validation Check button.
    10. After entering the Git repository information and authentication details, click the Connection Test button.
    11. When the Next button is enabled, click the Next button.
      ItemExplanation
      URL input methodSelect the URL input method.
      • Select from the list: the ArgoCD tools registered as tools will appear.
      • Enter manually
      ArgoCD URLAfter entering the ArgoCD URL, click the Confirm button. The Authentication Information area appears.
      Authentication informationEnter Authentication Information and click the Connection Test button. The Application Basic Information area opens.
      Application nameEnter the name of the ArgoCD application to create in ArgoCD.
      Project nameEnter the project name of the ArgoCD application.
      Repository typeSelect the repository type.
      • Create a new repository with Helm chart: Use a Helm chart to create a Git repository for GitOps. Helm chart information area opens.
      • Use existing Git repository
      Helm chartPlease select a Helm chart.
      Helm chart Git repositoryEnter the information for the Git repository to be used by GitOps.
      Table. New App Creation Settings

    Use existing App

    To configure the target deployment environment using an existing ArgoCD application, follow these steps.

    1. Target deployment environment screen, enter ArgoCD URL, then click the Confirm button.
    2. The screen for entering the existing ArgoCD application name and credentials appears.
    3. Enter the Existing Application Name and Authentication Information, then click the Connection Test button.
    4. A URL Check popup window opens to distinguish the Git repository linked to the ArgoCD application..
    5. URL Check After editing the Base URL in the popup window, click the Confirm button.
    6. The Git repository information associated with the ArgoCD application is displayed.
    7. Enter the authentication information for the Git repository, then click the Connection Test button.
    8. Enter the yaml file name and key value to change in the Manifest Root path area.
    9. When the Next button is enabled, click the Next button.
      ItemExplanation
      URL input methodSelect URL input method
      • Select from list: ArgoCD tools registered as tools appear.
      • Enter manually
      ArgoCD URLAfter entering the ArgoCD URL, click the Confirm button. The Existing application name and credentials section will appear.
      Application name / authentication informationEnter the Existing application name and credentials, then click the Connection Test button. The Git repository and ArgoCD information area appears.
      URL CheckSeparate the Base URL and Path in the full URL.
      Git repository credentialsEnter the credentials for the Git repository used by the selected existing application.
      Image Repo KeyEnter the path to the Yaml file that records the image repository information and the Key value. If the key values for repository and tag are the same, enter the same value.
      Image Tag KeyEnter the path to the Yaml file containing the image tag information and the Key value. If the repository and tag have the same key, enter the same value.
      Image Secret KeyEnter the path to the Yaml file containing the image secret information and the Key value.
      Deploy Strategy KeyEnter the path to the Yaml file containing deployment strategy information and the Key value (optional).
      Table. Existing App usage configuration items
    Reference
    The ArgoCD deployment project in the DevOps Console performs deployments by modifying the information registered in the Image Repo Key, Image Tag Key, Image Secret Key, and Deploy Strategy Key.

    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 pipelineDisplays build/deployment pipeline information.
      • The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
      CategorySelect the development/operation distinction.
      • The permissions for the pipeline vary according to the development/operation distinction.
      URLSelect Jenkins to configure the pipeline, then enter the job name.
      • The Jenkins instances available to the user are displayed.
      Build AgentSelect the agent to be used for pipeline builds.
      Build environment OSDisplays the OS information of the environment in which the build agent runs.
      User informationIDP 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 variablesSet the environment variables to be registered in the Jenkins pipeline.
      Image Tag PatternSelect the tag assignment method for the container image.
      Deploy StrategySelect the deployment method for the container image.
      Recipient of deployment resultsSelect 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.
      ItemExplanation
      Dockerfile configurationCreate 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 pathSpecify the Dockerfile file path in the source code.
      Branch nameThe branch name is automatically registered when you set it in Code Repository Configuration.
      DockerfileCheck and modify the contents of the Dockerfile.
      pipeline scriptCheck and modify the pipeline script.
      Table. Project Creation Custom Settings Items
    Note
    For detailed information about Jenkins pipeline scripts, see the official site.

    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.
    Notice
    It cannot be canceled during creation, and when the project is created successfully, the Confirm button becomes active.