Modernization Platform v2.3.0 GA Release

Modified on: 2025-04-08 13:53

TABLE OF CONTENTS

New Feature
Enhancement
Bug Fix

New Feature

Cluster-specific Prometheus agent integration

Prometheus, which was previously created for each project in each cluster for monitoring, has been integrated into one per cluster. As a result, resource usage for Prometheus agent in the data plane and Cortex in the control plane has been reduced.

Transition to Loki-based integrated logging service

The logging service provided through the existing EFK stack (elasticsearch, fluentbit, kibana) has been changed to a Loki and Promtail-based service. When using Loki, in most cases, you can save control-plane resource usage compared to Elasticsearch. The log search and visualization service for the logging service is integrated with Grafana, the same as the monitoring service, so some log-related dashboards are provided, and you can also configure the dashboard and search the logs required for the application.

It provides installation of add-ons for Istiod, Istio Ingress Gateway, Jaeger, kiali, and prometheus, and provides automated connection settings between each service during installation. In the case of Kiali, it provides authentication/authorization functions through the Console's User.

Improved yaml editor functionality in Console

The yaml editor component for viewing or editing yaml files in the console has been changed. The editor provides various functions such as viewing mini maps, indentation, typo and grammar check, etc.

Added the ability to register applications and build pipelines using Container Images

A feature has been added to register applications as container images and build pipelines without an application build pipeline.

Added Editor mode when modifying Application configuration of Deployment Groups

When modifying the contents of the application configuration of the Deploy group, “Editor mode” has been added in addition to the UI mode where only items defined in the existing form can be modified. In Editor mode, a screen is provided where application-related specifications can be modified through the yaml editor.

Improved Deployment Group input in Console

In DeployGroup > Applications > Configuration, pod annotations and strategy items have been added to the Deployment Spec input contents.

In DeployGroup > Applications > Configuration, startup probe items have been added to Advanced > health check.

In DeployGroup > Resources > PVC, the storage class input item has been changed to a combo that allows text input.

Added taint and label setting function to dataplane node information in the console

A feature to set taints and labels for a node by modifying node information in System management > clusters > node has been added.

Added ability to edit Alertmanager settings

A feature has been added to allow modification of alertmanager settings that were previously only viewable in System management > Monitoring > Alertmanager.

Added ability to set up a repository for GitOps in Deployment Groups

Added the ability to set up a repository for gitops in Deployment Groups > Basic infro.

Added ability to edit Application's git target repository in Console

A field has been added to modify the Git Target repository in Application Details > Basic Info.

Enhancement

Adding permissions when creating a Robot Account

We have set up a robot account created when a project is created to have the ability to view lists of specific resources (Artifacts, Tags).

Provides option for deleting Argocd App when setting Prevent cascade delete option in Deployment Groups

If the prevent cascade delete option is set in DeployGroup, the application in argocd remains even when the application set in Deploygroup is deleted, so even if the workload deployed to the cluster is deleted, the user is asked to delete the part that argocd continues to deploy.

Added check logic to ensure that the Git source set in Deployment Groups is unique to Realm

If the Git Repo set in the Deploygroup is duplicated, files may be overwritten, so logic has been added to check whether the Git Repo address is unique across the entire Realm.

Modified DisplayName to be searched when searching Deployment Groups and Applications of Deployment Groups

When searching for Deploy groups and DeployGroup's Application, we have modified the part where only the registered Name is displayed and changed it to be searched by DisplayName (Name).

Changed the Application deployment status to be displayed in the Application Section of the Project's Dashboard.

The section that previously showed the latest build status of the application has been changed to show the latest distribution status.

Fixed managedFields not being visible when querying k8s resources in the console

We have fixed an issue where managedFields were retrieved when querying Kube resources in the console, making readability difficult.

Modified to improve readability when viewing Pod Logs in the Console

We have fixed the problem of no horizontal scroll and awkward line breaks when viewing logs in Console > Workload > Pods > Logs, and provide the Wrap Line function.

Deleting meaningless fields in Project Management Clusters

When viewing the Project Management > Clusters list, the meaningless Group field has been removed.

Improved handling of unintended errors in Storage

We have resolved the issue where an error would be displayed due to an incorrect API request when selecting Resource without selecting Cluster in the Storage screen in System/Project.

Adjusting the fields to be displayed on the Application, Delegate Group list screen

In the Applications, Deployment Groups list screen, Description has been removed and changed to display DisplayName (Name).

Adding a scrollbar to the project selection screen in Project Management

If a user is a member of many projects, a scrollbar is provided when selecting a project in Project Management.

When viewing the application deployment history of DeployGroup, specify the application being viewed as the title.

When viewing the history of Project Management > Deployment Groups > Applications, a history title has been specified to confirm the application being viewed.

Added DisplayName Sorting option when querying Application, DeployGroup list

Display Name has been added as a sorting option so that it can be sorted by Display Name when viewing the Application and DeployGroup lists.

Bug Fix

Solving the problem of number format exception occurring in the system dashboard of the console

Fixed a case where a number format exception occurred in the persistent volumes chart on the System Admin > Dashboard screen.

Fixed an issue where the build history disappears when changing the name of the build pipeline in the console.

We have fixed a feature that causes history to disappear when changing the name of an existing build pipeline.

Fixed an issue where the Save button was disabled when modifying the application health check of a deploy group in the console.

We have fixed the issue where the Save button would be disabled depending on the Method selected when modifying the Advanced > health check item in DeployGroup > Applications > Configuration.

Fixed an issue where the Docker build would intermittently fail during the application pipeline build.

Docker build가 5분 이상 넘어가는 경우 reconnect에 실패하여 권한에러가 발생, 빌드에 실패하는 문제를 수정하였습니다.

Fixed the issue where the harbor robot was not created when creating a project.

The issue where the harbor robot distributed via Argocd was not created when creating a project has been resolved.

Fixed an issue where failed deployments via Deployment Groups would remain in the deployment history as successful

We have resolved the issue where even if resource deployment to a cluster fails due to resource specs not matching, the actual deployment history is processed as successful.

Fixed an issue where UI allowed creation with a Pipeline name that was not allowed

Fixed an issue where UI and CICD would allow creation based on backend logic that does not allow characters such as spaces and '_' in the pipeline.

Fixing an issue where changing a privileged Git Secret does not apply the Secret

We have resolved an issue where Pipeline builds and application deployments would not work because the Secret in the Application/Deploygroup of the Console was not applied even if the account was changed to one with permissions.

Fixed an issue where previous deployments were still displayed as running when viewing deployment history.

We have resolved an issue where, when viewing the History of DeployGroup in the Console, deployments that had already been completed were displayed as if they were still running.

Fixed the issue where Write permission was not checked when performing Connection Test of GitOps repo

Fixed the issue where Write permission was not checked when performing Connection Test after registering GitOps Repo and Secret.

Fixed the issue where RBAC of user created when deleting Deployment Groups was not deleted

Fixed the issue where k8s permission set for member belonging to Project of DeployGroup when creating DeployGroup was not cleared when DeployGroup was deleted.

Fixed the issue where user settings are initialized when using Web-shell of Console

Fixed the issue where files such as .bashrc, .bash_profile are initialized when reconnecting when using web-shell of Console.

Fixed the issue where terminal size is not adjusted when executing web-shell of Console

Fixed the issue where the window size and internal content size of terminal of web-shell were unnaturally adjusted.

Logging (Kibana) access problem solved due to Too many redirects when accessing Kibana

If too many roles are assigned to the console, the Too many redirects error occurs in Kibana and the screen is not displayed.

Resolved the problem of incorrect layout when creating an Application Copy

The problem of incorrect screen layout alignment due to validation check in the Image Registry when copying an Application has been resolved.

Resolved the problem of not being able to modify the label of a Cluster Node

The problem of a 404 error occurring when setting a label in System Management > Clusters > Worker Node has been resolved.

Resolved the problem of the Deploy button being intermittently disabled when deploying an Application in Deployment Groups

The problem of the Deploy button being intermittently disabled when clicking on another Application deployment button after executing and canceling the deployment of an Application in a Deploy Group has been resolved.

Resolved the problem of information not being displayed when searching for a User in Groups

The problem of Roles, Groups, and Created fields not being displayed when searching for a user in Project Management > Administrator > Groups > Users has been resolved.

Fixed the issue where the status of the Pod deployed in the Console is displayed differently from the status of the Pod actually deployed

Fixed the issue where the status of the Pod in Project Management > Dashboard and the Pod deployed in Dataplane are displayed differently for certain statuses.

Fixed the issue where the settings for Cluster, Namespace, and Filter selected by the user in the Workloads/Networking/Storages menu remain even when the Project is changed.

Fixed the issue where the StorageClass resource, which is a global resource, is exposed in the Storages menu of Project Management.

Fixed the issue where a 400 json error occurs when modifying and creating settings with YAML in Workloads/Networking/Storages

Workloads Resource Deletion Successfully Fails Message and List Refresh Issues Fixed

When deleting resources from Workloads, a Fail message is displayed even if the deletion is successful, and the resource list is not automatically updated when adding resources.

Fixed the issue where the Ingress URL link in Deployment Groups is displayed abnormally

Fixed the issue where the ingress url in the dashboard is not displayed properly when the ingress resource created in the Ingress tab of Deployment Groups has multiple domains and paths.

Fixed the issue where the build and deployment are not performed properly when the Application and Deployments Group names are the same

Fixed the issue where the Git repo secret is overwritten when the Application and Deployments Group names are the same, preventing the build and deployment.

Fixed the issue where the log is not displayed when the git-clone step takes a long time during the pipeline build

Fixed the issue where the log is not displayed when git-clone takes a long time during the pipeline build of Applications.

Fixed the issue where the cache size cannot be changed

Fixed the issue where the cache is enabled in Applications > pipeline, and the size cannot be set.

Fixed the issue of TLS secret designation failure during Ingress deployment

Fixed the issue of manifest being created without secret even when specifying TLS secret when configuring Deployment Groups > Ingress deployment spec.

Fixed the issue of abnormal deletion behavior when multiple projects have applications with the same name

Fixed the issue of applications in other projects being deleted when designating and deleting applications with the same name in multiple projects.

Fixed the issue of web-shell not being executed when the user name includes . or starts with 0

Fixed the issue of 404 error page occurring when logging in to the console in certain situations

Fixed the issue of moving to the 404 page when clicking the login button after leaving the console page unattended for more than 30 minutes without logging in.

Fixed the issue of pipeline name changing after pipeline creation

Fixed the issue of allowing the pipeline name to be modified after pipeline creation.

Online consultation

English