Create and Manage Applications

An application is the basic unit for managing all settings and history required for deployment. In the Applications menu, you can create, view, modify, and delete applications.

Create application

Create a new application by configuring the deployment target cluster and source information.

1. Go to the KakaoCloud console > Developer Tools > Deployflow.

2. In Applications, click [Create Application] in the upper-right corner.

3. Enter the required information.

4. When all settings are complete, click [Create].

   Category	Item	Description
   Basic information	Application name	Enter an application name
   	Application description	Enter an application description within 100 characters
   Cluster information	Deployment cluster	Select the target cluster where the application is deployed Only clusters with a public endpoint and Provisioned status can be selected
   	Namespace name	Enter the namespace where resources are created
   Source information	Source repository	Select the repository where the deployment source is located
   	Source branch	Select the branch or revision where the deployment source is located
   	Deployment method	Select Raw Manifest, Kustomize, or Helm, and enter the path where the file is located
   Approval settings	Approval setting option	Select whether to use an approval stage before deployment When approval settings are enabled, sync or rollback operations can be run only after all approvals are complete If an approval request is in progress, you cannot disable the approval setting option by changing it to Not used
   	Reviewer	Specify reviewers who approve the deployment when approval is enabled You can configure at least 1 and up to 5 reviewers
   Advanced settings	Resource deletion option	Select a deletion option for child resources during sync or deletion
   	ServerSideApply option	Select whether to use Server-Side Apply when applying Kubernetes resources Applications using the ServerSideApply option cannot run Force Sync

You can select one of the following resource deletion options.

Option	Description
Foreground	Deletes all related child resources before deleting the application.
Background	Deletes the application first, then deletes child resources sequentially.
Non-cascading	Deletes only the application and keeps child resources.

Caution

If you delete a cluster or repository and then recreate a cluster or repository with the same name, an existing application may encounter an error or connect to the newly created repository.

Tutorial

For an example of connecting a Codeflow repository manifest path to a Deployflow application using Raw Manifest and synchronizing it, see Build a CI/CD pipeline with Codeflow and Deployflow.

View application list

View the status, sync status, deployment strategy status, and source information of created applications in the list. The list also provides shortcuts to management pages for related resources such as deployment clusters and source repositories.

1. Go to the KakaoCloud console > Developer Tools > Deployflow.

2. Select Applications to view the list.

   Item	Description
   Name	Name that identifies the application
   Description	User-entered description of the application purpose or characteristics
   Sync status	Whether repository settings and actual cluster resources match
   Status	Current Health Status of Kubernetes resources
   Deployment strategy status	Current stage of the deployment process, such as Blue/Green or Canary
   Cluster	Deployment target cluster information and shortcut link
   Source	Codeflow repository information and shortcut link
   Creator	User who created the application
   Last sync time	Most recent time when synchronization was performed
   Creation time	Time when the application was created

View application details

View an application's settings, deployment progress status, resources, and history in the details screen.

1. Go to the KakaoCloud console > Developer Tools > Deployflow.
2. In Applications, select the application whose details you want to view.

In application details, you can check details, approval information, deployment strategy, resource status, and history. The top action area provides action buttons based on the deployment stage.

Deployment actions

Deployment actions provide only the core button required for the current deployment stage. The default flow proceeds in the order of sync, promotion, and deployment completion. The promotion stage is provided only when a Blue/Green or Canary deployment strategy is applied.

Action	Provided when	Description
Request sync approval	The approval-before-deployment option is enabled	Requests reviewer approval before synchronization. When all reviewers approve, this changes to the Sync button.
Sync	Resource updates are detected	Analyzes differences between the target environment and source code and aligns resources.
Promote	Synchronization is complete in a Blue/Green or Canary deployment strategy	Applies the synchronized new version to production traffic. After promotion is complete, the flow returns to Request sync approval or Sync when a new update occurs.

Application management buttons are always provided. Approval settings configures whether to use approval procedures in the deployment process and who has approval permissions. Modify changes application details. Delete removes the application from the system, including related resources and history data.

Details

Check the application's basic information, deployment target, source, and deployment method settings.

Item	Description
Name	Name that identifies the application
ID	Application ID
Description	User-entered description of the application purpose or characteristics
Creator	User who created the application
Deployment cluster	Kubernetes cluster information
Namespace name	Namespace where resources are deployed
Status	Status value
Sync status	Sync status value
Source repository	Codeflow repository information
Source branch	Branch information where the deployment source is located
Deployment method	Selected source type among Raw Manifest, Kustomize, and Helm
Path	Path where the deployment configuration file is located When using Helm, setting a Chart.yaml stored in Git or a path containing a chart loads Helm templates
Resource deletion option	Resource deletion policy setting
ServerSideApply	Whether the Server-Side Apply option is used
Last sync time	Most recent time when synchronization was performed
Creation time	Time when the application was created
Image	Image path

Helm

You can load manifests configured with Helm. If you specify a Chart.yaml stored in Git or set a path containing a chart, Helm templates are loaded. Enter the values settings enabled for Helm. You can also directly enter values.yaml content without using Git.

Approval information

When approval settings are enabled, the approval ID, requester, and status are displayed. If the approval status is Ready, the sync or rollback button is enabled.

Item	Description
Approval ID	Approval ID
Approval requester	User who requested approval
Operation type	Operation type subject to approval, such as sync or rollback
Approval status	Approval status value

Deployment strategy

This area is enabled when an advanced deployment strategy, such as Auto sync, Blue/Green, or Canary, is configured. It controls the current deployment progress. In the application details screen, click [Deployment strategy settings] and select one of Auto sync, Blue/Green, or Canary in the pop-up window.

Auto sync

Auto sync is a deployment type that automatically applies changes from the source repository to the cluster without a separate sync action when changes are detected.

When you select Auto sync in the Deployment strategy settings pop-up window, it is activated immediately after saving without additional configuration items.

When auto sync is configured, changes are applied to the cluster without a separate sync action. For rollback constraints, see History.

Blue/Green

Blue/Green is a deployment policy that configures deployments for the currently running version (Blue version) and the new version (Green version), then switches traffic from the old version to the new version at once.

When you select Blue/Green in the Deployment strategy settings pop-up window, configure the following items.

Setting item	Description
Deployment name	Select the deployment where the Blue/Green deployment strategy is applied.
Service name	Select the service used for traffic switching.

• Traffic switching: In the [Deployment strategy settings] pop-up window, select the environment that should receive live service traffic, Blue or Green, and click [Save]. Traffic switches to that environment immediately. If you select Green, traffic switches to the new version immediately, so choose carefully before applying it to production.
• Promotion and promotion cancellation: Blue is the existing version currently in service, and Green is the newly deployed version. When you click [Promote], select the environment to apply, Blue or Green. If you select Green, the new version (Green) is finalized and resources for the existing version (Blue) are removed. If you select Blue, promotion is canceled, resources for the new version (Green) are removed, and the existing version (Blue) remains.

Tutorial

For an example of applying a Deployflow Blue/Green deployment strategy and switching traffic, see Implement a Blue/Green deployment strategy with Deployflow.

Canary

Canary is a deployment policy that routes part of live traffic to the deployment of a newly deployed version to test whether the new version works normally. If an issue occurs, you can respond quickly. Because two versions coexist, it can also be used for A/B testing.

When you select Canary in the Deployment strategy settings pop-up window, configure the following items.

Setting item	Description
Deployment name	Select the deployment where the Canary deployment strategy is applied.
Service name	Select the service connected to the deployment where the Canary deployment strategy is applied.
Ingress name	Select the ingress used to route Canary traffic.
Number of Canary pods	Enter the number of pods to run as the Canary version. You can configure from 1 to 99, and the maximum number of pods may vary depending on Kubernetes resource status.
Traffic ratio	Enter the initial traffic percentage routed to the Canary version, from 0 to 100.

• Traffic ratio adjustment: Click [Adjust ratio] in the details screen and change the traffic ratio value to adjust the Canary traffic ratio in real time.
• Promotion and promotion cancellation: Origin is the existing version currently in service, and Canary is the newly deployed version. When you click [Promote], select the version to apply, Origin or Canary. If you select Canary, the new version (Canary) is finalized and resources for the existing version (Origin) are removed. If you select Origin, promotion is canceled, resources for the new version (Canary) are removed, and the existing version (Origin) remains.

Deployment strategy status

You can check the current progress stage of the advanced deployment strategy in the deployment strategy status.

Status	Description
None	Advanced deployment is disabled and normal deployment is available.
Auto	Automatic synchronization status.
Stable	Stable state where no deployment strategy is running.
Blue Active	Blue/Green deployment is in progress and traffic is routed to the Blue version.
Green Active	Blue/Green deployment is in progress and traffic is routed to the Green version.
Canary Rollout	Traffic is distributed between the existing and new versions according to the configured ratio.
Promoted	Promotion is complete, deployment is finalized, and the previous deployment is removed.
Cancelled Promotion	Promotion is canceled and the new deployment is removed.

Resources

You can check the relationships between deployed resources as a topology graph. When you click an individual resource, you can view summary information and manifest information. Topology cards display revision information by resource, and view controls such as zoom, layout switching, and refresh help you explore resource structures.

History

You can view previous deployment history as a list. You can view previous settings or roll back to a specific point in time. For each history item, you can view manifests in a code editor format, with changed lines and failure reasons.

Rollback constraints

In the following cases, the rollback button is not provided in the History screen, so you cannot roll back or create a rollback request.

• A Blue/Green or Canary deployment strategy is configured.
• The deployment type is configured as Auto sync.

To perform rollback, disable the deployment strategy by setting it to None, then proceed.

Modify application information

Modify editable information such as application description, source information, and deployment settings.

1. Go to the KakaoCloud console > Developer Tools > Deployflow.
2. In Applications, click the [⋮] button for the target application, then select Modify.
3. After completing the changes, click [Modify].

Caution

The deployment cluster cannot be modified after application creation. To change the cluster, create a new application.

Delete application

Delete applications and related deployment history that are no longer used.

1. Go to the KakaoCloud console > Developer Tools > Deployflow.
2. In Applications, click the [⋮] button for the target application, then select Delete.
3. In the popup, enter the deletion phrase, then click [Delete].

Caution

Deleted application resources cannot be recovered.