Skip to main content

Create Project and Profile

Project Creation and Settings​

note

Only users with ADMINISTRATOR privileges can manage project settings

This guide explains the registration, configuration, and management of permissions for projects in AMDP. Projects can only be registered by SYSTEM ADMINISTRATORS . After a system administrator creates a project, users with administrative rights can be assigned. Individual users (DEVELOPERS) can be granted user permissions (read/write/execute) for specific profiles/applications. ADDitionally, it covers GIT management for profile settings and application repositories, and Image Registry Management for container-built images. Regular users registered as project administrators can manage and view the project, including its permissions and environment. For detailed information on the range of granted permissions, refer to the User Permission Management section.

Project Creation​

  1. Select the Project Management menu. Click the ADD button in the project management list to go to the new project creation page.

  1. On the project Addition page, enter the project name and an optional description. Click SAVE to create a new project.

  2. The created project appears as below. Admin rights and User rights are set after registering users.

Project Settings​

note

Administrator rights and user rights settings are done during user or group creation setting.

GIT Settings
note

The Git information in this example is not real. All Git information must use actual user details.

  1. You need to ADD repositories for profile configuration and application storage for the new project created. Click the ADD button in the profile config Git list.

  1. Add repository info for profile settings. Use the Validate button to check the settings. If the connection is normal, successfully connected will appear in the validation result.
note

For Github, a (developer) token is required instead of a regular user password due to policy.

  1. Add repository info for the application storage. Again, use the Validate button for checking.
note

For Github, a (developer) token is required instead of a regular use password due to policy.

Image Repository Settings
  1. You need to add an image registry for storing container images of applications registered in the new project. Click the ADD button in the image registry list.

  1. Add image registry information. Use the “Validate” button to check the settings.

Profile Creation and Configuration​

note

Only accounts registered as Project Administrators can create profiles. System Administrators can only view and need to be registered as a project administrator to have permissions .

Creating a new Profile​

  1. Select new project created from the projects menu. Click the ADD button or the ADD Profile button in the top right corner.

  2. On the Create Profile page, enter Develop in the Profile field and check for name duplication using the button on the right.

  3. Write the desired content in the Description.

  4. Register the profile setting repository listed in Project Management in the Git Repository field.

  5. Register the registry listed in Project Management in the Image Registry field.

    The project must be previously registered in the Image Registry.

  6. Select the cluster to be used by the profile. A cluster is a mandatory item after installing AMDP.

  7. Do not use Topology Type for this guide. Select NONE .

  8. After filling in all details as shown below, click the Save button.

  9. Successful profile creation will redirect to the profile detail page.

Basic Profile Configuration​

note

Only accounts registered as Project Administrators can Add SERVICES. System Administrators can only view and need to be registered as a project administrator to have permissions .

note

ADDON SERVICES must be pre-registered through the Addon Service Management menu after installing AMDP. Refer to the installation guide for more details.

Adding ADDON SERVICES
  1. Select the ADDON SERVICE tab on the profile detail page. Click the ADD button in the Addon Service list to register a new Addon.

  1. Register Tekton for CI. Select CICD in Type.

  2. Choose Tekton in Name.

  3. Enter desired content in Description.

  4. Click the Save button at the bottom right.

  1. Register argocd for CD. Select CICD in Type.

  2. Choose argocd in Name.

  3. Enter desired content in Description.

  4. Click the Save button at the bottom right.

CICD Settings
note

Only accounts registered as Project Administrators can set up CICD. System Administrators can only view and need to be registered as a project administrator to have permissions .

  1. Select the CICD tab on the profile page. Click the Edit Settings button in the project deployment settings.

  1. Choose” Tekton + ArgoCD” for the Pipeline Type.

  2. Click the ADD Tekton Pipeline button and select tekton-base-202301/maven-ci (Role: CI, Supported Framework: SPRINGBOOT) .

  3. Click the ADD Tekton Test button and select all tasks below: a. tekton-base-202301/git-cli (Role: CI, Supported Framework: SPRINGBOOT, VUEJS, REACT, NEXTJS, NEXACRO,DOCKER) b. tekton-base-202301/git-clone (Role: CI, Supported Framework: SPRINGBOOT, VUEJS, REACT, NEXTJS, NEXACRO, DOCKER) c. tekton-base-202301/maven (Role: CI, Supported Framework: SPRINGBOOT)

  4. Click the Save button at the bottom right to save the settings.

APPLICATION Registration

Refer to section “Create Application”

INGRESS Settings

You configure ingress to access the application from outside after deployment. Before setting up ingress, a domain that can be accessed must already be registered.

  1. Select the INGRESS tab from the profile list.

  2. In the ingress list, press the ADD button to create a new ingress.

  3. Enter hello-amdp-ingress in the Name.

  4. Select hello-amdp-develop in Namespace and press save.

  1. After saving, you are automatically redirected to the ingress detail page. Initially, there is nothing under Hosts. Press the ADD button with the red circle to ADD items as shown in the Ingress Detail Page image below.

  2. Enter the domain to register in Host.

  3. If TLS setup is necessary, press the 🖊 button next to TLS Secret (optional) to select a registered TLS Secret. TLS setup is not used in this guide.

note

For TLS setup, it must be previously registered in the Kubernetes resource Secret.

  1. Press the ADD button under Target Microservice to register a path.

  1. Select the application (hello-amdp-blue) to assign to the ingress and enter the toplevel path (“/”). Press the save button, and as shown in the image above, the settings are complete. Finally, press the Save button at the bottom right to complete the ingress registration:

  1. After saving, click on hello-amdp (develop profile) at the top. If you go back to the INGRESS tab, you can see the registered ingress as shown in the image below.

  1. Currently, you have only registered, so you need to deploy to the actual Kubernetes ingress resource. Press the Deploy button to deploy.

  2. Check for normal deployment in the deployment status, and the ingress setup is completed.

  3. Test Result.