Modernization Platform v2.1.0 GA Release

MCMP 통합계정 Modified on: Mon, Apr 7, 2025 at 6:42 PM

NEW FEATURE
BUG FIX

NEW FEATURE

Improved Application and Deploy Group query functions

The ability to view resources in the Application and Deploy Group menus has been improved.

Application List Page

Added the ability to search by Application Name on the Project Dashboard > Application list page.

Deploy Group List Page

Added the ability to search by Deploy Group Name and Namespace on the Project Dashboard > Deploy Group list page.

Deploy Groups > Applications

Added ability to search and page by Application Name in the Applications tab of a Deploy Group.

Deploy Groups > Resources

Added ability to search and page by Resource Name to the Resources tab of the Deploy Group.

Deploy Groups > Ingress

Added ability to search and page by Ingress Name to the Ingress tab of a Deploy Group.

Added the ability to search for users by Login ID on the System Dashboard > Users screen.

Added list refresh feature to Add-on installation screen

A button has been added to the Add-on list screen to refresh the installation status.

Improved Ingress configuration features

Improved functionality that can be set in the Ingress tab of the Deploy Group.

Directly enter the Service name in Ingress

The Ingress Path service name has been improved so that it can be entered directly rather than just selected from the list.

You can select the Application to be deployed in the Application tab or directly specify a Service that the user has created separately.

Ingress PathType setting support

You can set the Ingress PathType when deploying Ingress in the Deploy Group.

Prefix, Exact, ImplementationSpecific, and Default is ImplementationSpecific.

Support for Ingress Class settings

You can specify an Ingress Class when deploying Ingress in the Deploy Group. The Ingress Class must be deployed to the dataplane to be deployed, and if not selected, the Ingress class set as default in the dataplane cluster will be used.

Support for using ACM TLS

Supports using certificates registered in ACM for TLS Offloading in ALB Ingress Controller.

If you are using ACM, you should check the TLS configure option and save it without selecting TLS Secret.

Instead of TLS Secret, the ACM Arn specified in Annotation will be used.

Added Prevent Cascade Delete option when deleting a Cluster in DeployGroup

When deleting a cluster from DeployGroup, select whether to clean up the cluster's deployed resources.

Enabled (Default): When a Deploy Group is deleted or a Cluster is removed from a Deploy Group, the Resources and Namespaces deployed to the Cluster are not deleted.
Disabled: When a Deploy Group is deleted or a Cluster is removed from a Deploy Group, the Resources and Namespaces deployed to the Cluster are deleted.

Depending on whether the option is selected, a different confirmation message is displayed when deleting a cluster in Deploy Group > Clusters.

Added ability to specify a Branch when building an application

Added the ability to run a build by specifying a Git branch when performing a build.

If you check the option for the Branch item in the Pipeline settings screen, you can enter a Branch when requesting a build.

You can use the Branch specified in the Pipeline settings screen as the default, and enter the Branch name if you want to build a different Branch.

Added option to use cache when building application

In Application > Build Pipeline, decide whether to use Cache during build. Using Cache can improve build execution speed, but since it reuses resources used in the build, it can cause unexpected errors when used, and there are restrictions on concurrent builds and changes in storage size.

A new version of NodeJs is available

When selecting npm build in Application > Build Pipeline > Build Tool, selectable Node Versions are added. (node15,16,17,18)

Improved speed when viewing already completed Build Logs

When querying the log of an application that has completed a build, the speed has been improved by receiving it as a string rather than a stream, and it is provided to the user in a readable format.

User Tag feature of Application, DeployGroup

Provides user Tag functionality in Application and DeployGroup.

[Edit Tag]

You can register tags in key/value format in the Basic Info screen of the Application, DeployGroup resource. If you register the same key, it will be overwritten.

[Tag search]

Filters are provided on the search screen for each resource. When you select Tags, you can search for the tag keys of the resources registered in the project. You can search by selecting the key or by directly entering it in the key:value format.

Application copy function

You can create a new application using an already created application. The copy function can copy based on the Source Project or Target Project.

[Copy from Source Project]

After selecting the application to copy with the checkbox, go to the Copy page by clicking the Copy Application button.

[Copy based on Target Project]

Go to the Copy page through the Copy Exist Application button in Application > New Application.

In the Copy Application screen, information on the Source/Target Project is automatically entered according to the entry path, and information on the copy target Application is included depending on whether the Application is selected. You can copy by modifying the newly created Application name and the Image registry information where the Image is to be stored based on the Source Application. Copying is performed through the Create button.

Added HostAlias feature

Provides the ability to specify HostAlias through Deployment Group > Application > Configuration > Etc.

You can specify HostAlias for the application to be deployed by specifying the IP and Host Name (Domain).

Added mail sending function

A feature has been added to notify relevant personnel by email when a project creation request, project member join request, or project setup is complete.

When a project creation request or setup is complete, users with the project-administrator or global-administrator role will receive an email.

When a project join request is made, users with the project-administrator role for the project will receive an email.

Project Creation Request

When you request a project creation in New Project > Request to create a project, you can receive the following email.

Project setup complete

You can send a project settings completion email by clicking the E-mail button in the corresponding project item in System Dashboard > Projects.

Project Join Request

If you request to join a project in New Project > Request to Join a project, you will receive an email like the following.

In the Tool list, Default has been changed to allow only one Tool type to be specified.

The Tool specified as Default is used in the system menu.

If it is disabled (Enable is Off), the menu that uses the Tool is also disabled.

Change the process for project status changes

The process for changing the status of a project has changed.

The project creation event is fired when the status of a project changes from Requested to Running.

Once a project is in Running status, it cannot be changed to Requested.

We have changed the process that could not be used without the approval of the system administrator when registering users (Self Registration).

Even if a user registers directly, the status is automatically approved, and the project administrator can immediately invite them to the project.

Monitoring AlertManager config and Rule setting query function

You can view the configuration of AlertManager and the set Rules through Monitoring > AlertManager and Rules.

You can check the settings query and detailed information by looking up Rules.

Added ability to assign permissions to monitoring Main org

You can assign SystemAdmin, SystemEditor, and SystemViewer roles to Grafana in Roles > Tools Permissions. When you grant a user the role, the user will be added to the Main org and will be granted the permissions appropriate to the role.

We have improved the screen and functions for menu management in System Dashboard > Platform > Menus.

We have separated the System Menu and Project Menu into tabs, and made it possible to intuitively distinguish between the Main Menu and Sub Menu.

Additionally, when registering a new menu in the menu, the registered menu is now displayed with the default icon.

Upgrade Grafana version

Grafana version has been upgraded to 8.5.3.

MCM Backend 재개발

We have redeveloped the MCM Backend in GO Language to facilitate future maintenance.

Display product version at the bottom of the screen

The current version of the Modernization Platform is displayed at the bottom right of the screen.

BUG FIX

Improved the phenomenon of unintended screen refresh by users when authentication token time expires in the ZCP console

We have fixed the issue where the screen would refresh and the content being worked on would be lost when the user's authentication token expired.

We have resolved the issue where data prior to modification would be displayed when menu information was modified and saved.

Fixed a bug where you could request to join a project that you were already a member of

You can now request to join a project you are already a member of, and we have resolved an issue where the approval status would be released when you requested to join.

Fixed a bug that caused a 500 error when saving a role.

Fixed a bug that caused a 500 error due to missing API parameters when saving some Roles.

Fixed a bug where Kubernetes permissions were not granted to the Namespace even when a Deploy Group was added.

Fixed a bug where users were not granted permissions to the Namespace of a newly added Deploy Group even if they had Kubernetes permissions.

Fixed a bug where some resources were not being deployed via GitOps.

We fixed a bug where the Operator incorrectly creates the argocd namespace string.

We fixed the problem where the secret name used in argocd is created identically when the application and deploygroup names are the same, and the secret is overwritten.

Fixed a bug that occurred when a previous build was running when running a build.

We have fixed an issue where the next build would not be performed due to a timing issue with the history update of the previous application when performing an application build.

Fixed a bug where finalizers would continue to be added when Argocd Application deletion failed.

Fixed a bug where the same finalizer would be added infinitely when deleting an Argocd Application failed.

Fixed a bug where adding a cluster to DeployGroup would result in an error by requesting the wrong mcm namespace.

Fixed an issue where MCM was being requested using an incorrect Namespace value when adding a cluster to a DeployGroup.

Fixed a bug where an error pop-up would appear in the Build History dialog for builds stopped with Abort

We have resolved the issue where an error pop-up would appear when viewing history depending on the status of the Pod performing the build during an application build.

Fixed a bug where the system label of ZcpApplication was deleted when modifying pipeline information.

Fixed a bug where system labels used by ZCP would be deleted when changing the application's pipeline settings.

Fixed a bug where the Display Name of ZcpApplication and DeployGroup was not displayed in the list view.

Fixed an issue where Display Name was not displayed when viewing the Application and Deployment Group lists.

Fixed an issue that occurred due to not handling errors that occurred when adding a cluster to DeployGroup.

Fixed a bug that caused Quota lookup to fail on the Overview screen of the Deploy Group.

We fixed a bug where a 500 error occurred due to incorrect parameter creation when searching for Quota on the Deploy Group Overview screen.

Fixed a bug where the quantity was incorrectly displayed in the Deploy Group list screen when changing a project.

We fixed a bug where the number of Deploy Groups from the previous project was displayed when changing a project while the Deploy Group list screen was displayed.

Fixed a bug where the number of installed Add-ons was displayed incorrectly in the Add-on screen.

A bug where the number of Add-ons already installed was displayed incorrectly in Installed on the Add-on screen has been fixed.

Fixed an issue where Grafana tool permissions were not granted in the System Administrator Console menu.

Fixed a bug where prometheus was deleted when adding a cluster to DeployGroup

We have resolved the issue where Prometheus was unintentionally deleted when adding/deleting a cluster to DeployGroup.

Fixed a bug where Kubeconfig could not be retrieved when there was an issue with the cluster.

Fixed a bug where Kubeconfig could not be retrieved when there was an abnormality in the cluster status (e.g. Node Not Ready).

Fixed a bug where a Cluster remained in the Deploy Group even after removing it from the Project.

We have fixed a bug where a cluster would remain in the Deploy Group and be deployed even if the cluster was removed from the Project.

When a cluster is removed from the Project, it is also removed from the Deploy Group, and the Namespaces and Resources deployed to the cluster are processed depending on whether the Prevent Cascade Option is set. It is deleted only when the option is disabled, and remains when it is enabled.

Fixed a bug where Kube Permission was not added

Fixed a bug where selecting and adding a Resource in the Kube Permission tab of Role would not add it to the table.

Fixed a bug where all users were displayed in the Member Invitation Text

Fixed a bug where the entire user list would be displayed when the value for the search Text for inviting a project's Member was empty.

Fixed a bug where Cluster could not be deleted even if the Cluster Administrator role was present.

Fixed a bug where Cluster deletion was not possible due to insufficient permissions even if you had the Cluster Administrator system role.

Fixed a bug where permissions were not linked to Kibana Role when creating a project.

Fixed a bug where the Modernization Platform Role was not linked to the Kibana Role when creating a project.

Fixed the issue where server information was exposed on some error pages.

Enabled the use of secure headers and secured cookies.

Fixed the phenomenon where the kubernetes permissions of the Effective role reflected by the Group were not reflected

Fixed a bug where the kubernetes permissions of the Effective role reflected by the Group were not properly reflected to the user.

Add permissions to Kubernetes Resources

Some resources in Kubernetes require permission to subresources to use functions such as querying resource logs and executing them. We have added permission to additional subresources that were previously missing.

Fixed a bug where the Project Monitoring link would not appear in the System Dashboard > Monitoring menu.

Modify to propagate the realm creation event to each backend when the realm is created.

We improved the Realm created event propagation at the time of Realm Initialization so that the Realm default settings and the Realm scope monitoring alertmanager settings and alert rule registration are automatically set.

English