Modernization Platform v2.0.1 GA Release

Print

New Features


Added the ability to set parameters during Docker build

You can run the build by adding Docker build options.

You can set different parameters for each pipeline.

Added ability to stop build while build is running

You can immediately stop a running build by clicking the Stop button in the running build log screen or the build history screen.

Added ability to build applications without building images

Added the ability to build applications without building images.

You can create libraries and push them to repositories like Nexus or Artifactory.

If you uncheck Image Build, you can build applications without creating images.

Added the ability to check if the credentials set in the Image Registry are accessible

You can use the Test Connection button to check if you can access the Image Registry.

Support for Gradle 7.X version

Supports versions 7 and above when configuring Gradle builds.

NPM build support

Supports npm build tool.

You can select npm version and check whether npm is installed to perform build.

Improved so that other manually written Resource yaml can be deployed in addition to the Deployment and Service automatically generated in the GitOps Respository.

When using the deployment function of Deployment Group, the phenomenon of Resource Manifests uploaded directly by users for automatic deployment being deleted has been improved.

The deployment function in the Deployment Group generates and uploads deployment and service manifests. If you want to upload resources using the deployment function, you can upload the manifest to the path where the deployment and service are deployed and deploy it.

Added a feature to set ConfigMap and Secret as envFrom when setting Application Spec in Deploy group

When setting up Application Spec in Deployment Groups, we added a feature that allows you to set ConfigMap and Secret as envFrom without having to specify env key and value individually.

Added ability to specify the number of history to keep in builds and deployments

We added a feature to specify the number of history to be stored by specifying the history count during build and deployment.

If you specify the build history count in the Applications > build pipeline tab, only the corresponding number of build history will be stored.

If you specify a history count in the Deployment Groups > Applications tab, you can check the deployment history for that number.

Improved Add-on installation screen on clusters and automated handling of system parameters

System Dashboard > Clusters > Add-on Installation screen for the corresponding Cluster has been improved and a feature has been added to automate the input of some parameters during installation.

  1. Fluent-bit

2. Fluentd

3. Ingress-nginx

4. Prometheus

5. Prometheus-blackbox-exporter

6. Prometheus-k8s-events-exporter

Added the ability to add custom menus of URI type to the menu.

You can go directly to the link you set through the custom menu of the registered URI type.

Adding Istio Resource to Kubernetes Permission Management (Virtual Service, Gateway)

Added the ability to set access permissions for Istio resources (VirtualService, Gateway) in the Roles > kubernetes Permissions tab.

Changed the Application list on the Deploy Group dashboard screen to scroll when there are too many of them

In the Project Dashboard > Deployment Groups > applications tab of the corresponding Deployment groups, we have improved the screen so that it does not become too long and scrolls when the list of applications is too long.

Improved confirmation by entering the resource name when deleting a key resource

When deleting a cluster, project, application, or deploygroup, a deletion confirmation pop-up window is displayed, and deletion can be completed only after the exact resource name is entered.

Bug Fix


Fixed a bug where the Harbor Robot Account Secret was not automatically registered when creating a project.

When you create a project in the console, a project is also created in harbor, and a robot account that can be used when building applications is automatically registered. A bug where the Harbor Robot account secret was not registered due to a timing issue with the project creation has been fixed.

Fixed a bug where adding a user to the Administrator group in the System menu would not make them a system admin in Harbor.

When assigning Administrator group to a user, he/she should be granted all admin rights in zcp, but in harbor, a bug where he/she was not granted SystemAdmin rights has been fixed.

Fixed a bug where deployment requests were not made because the CI/CD application connection was not released.

Fixed a bug where CI/CD application connections were not released, causing deployment requests to fail and not work properly.

Fixed a bug in Readiness, Liveness where numeric type port numbers were generated as text

We have resolved the issue where the port number set through application deploy was created as text rather than a number type, resulting in an invalid manifest.

Fixed a bug where Advanced data was deleted when changing Application Spec in DeployGroup

We have fixed a bug where all previously set Advanced area data would disappear when modifying the Deployment Spec section when modifying Application yaml information in the Deployment Groups > Application tab.

Fixed a bug where groups from other projects were visible in the Project member list

When viewing the project member list, the issue where groups that member has in other projects were displayed together has been resolved.

Fixed a bug where Argocd Application was not added when adding a cluster.

Fixed a bug where Argocd Application was not created when adding a Cluster.

Fixed a bug where users were not given permission when adding/deleting a cluster to a Deploy Group.

We have resolved an issue where users were not granted access to the Namespace when adding/deleting a Cluster in Deployment Groups.

Fixed a bug where roles were not assigned to Kibana when creating a project or changing user permissions.

Fixed a bug where Kibana did not reflect the corresponding roles when creating a project or changing user permissions.

Fixed a bug where user-administrator in the system menu could not reset user passwords

Fixed a bug where a user-administrator with Admin privileges in the User Management menu was unable to reset user passwords.

Fixed a bug where Project participation request combo box would not display when the number of projects exceeded 10

The Project Participation Request combo box has been modified to display the full list of projects.

Fixed a bug where Prometheus was not installed when adding a cluster to a Deploy Group.

We fixed a bug where Prometheus, which collects metrics for projects, was not automatically installed when adding a cluster to deployment groups.

Online consultation

Contact us

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.