Saltware Supports K-Net's AWS Cloud-Native Transition
IT DAILY ·
✦ AI Summary
Saltware said on the 12th that it had transitioned K-Net's existing cloud operations system to AWS.
K-Net built a Kubernetes-based operating environment by applying Amazon EKS, Terraform, and Argo CD.
K-Net said it secured infrastructure that improved operational constraints and can respond to service expansion.
Saltware announced on the 12th that it had successfully transitioned K-Net's existing cloud operations system to AWS. K-Net has been operating services in its existing cloud environment since 2015.
However, as service expansion and operational sophistication progressed, the need for technical support and improved scalability grew, and K-Net pushed ahead with expanding Kubernetes-based services. As a result, K-Net needed a cloud environment with greater flexibility and more specialized operational capabilities.
Saltware pursued the AWS transition in line with those needs and analyzed the service structure and operational requirements. Based on that, it designed and built an optimized AWS-based architecture, and along with the AWS transition, it also built a Kubernetes platform based on Amazon EKS.
Saltware also supported the building and operation of cloud-native infrastructure based on Amazon EKS. The platform was built to reflect K-Net's service structure and operational requirements, and the design scope included the Kubernetes cluster, network, and application deployment environment. As a result, the previous server-unit, individual operating environment was transformed into a standardized, container-based operating environment.
K-Net introduced Amazon EKS, a fully managed service for simplifying Kubernetes cluster operations and supporting service management. This reduced the burden of cluster operations while securing high availability. It also established an infrastructure base that can flexibly scale in response to service demand.
K-Net standardized the configuration and deployment process to reduce the problem of relying on manual work by specific personnel in the existing configuration and deployment process. As a result, operational efficiency improved and stability also increased.
For infrastructure configuration, Terraform-based infrastructure as code (IaC) was applied. It also managed the code used in the infrastructure build process, securing standardization and reproducibility in environment configuration. In addition, it became possible to systematically manage changes.
For application deployment, Argo CD using the GitOps approach was applied. This allowed deployment status and change history to be managed around the Git repository. As a result, the deployment process was automated, operational visibility improved, repetitive manual work decreased, and a stable deployment system was established.
K-Net said that the AWS cloud transition improved operational constraints in its existing environment and secured an infrastructure capable of flexibly responding to service expansion. K-Net said that, with Saltware's support in the process, it built an architecture that met its requirements and showed a high level of satisfaction because ongoing support was possible through operations after the build.
Saltware explained that the project went beyond a simple cloud migration. Saltware CEO Lee Jeong-geun introduced the project as an example of transitioning K-Net's service operating environment to an AWS-based cloud-native structure, and said the company would provide continuous technical support from build to operations in the future and support a stable operating environment where customers can focus on service development and business.
Meanwhile, Saltware obtained certification for AWS's "Managed Service Provider Program" in September.
Source: IT DAILY · Kwon Young-seok
Original: https://www.itdaily.kr/news/articleView.html?idxno=242112
References
This article was produced with the help of an automated content generation algorithm.
Source: IT DAILY
View originalThis article was summarized and organized by BizCrush based on the original article from IT DAILY. For exact quotations and full details, please refer to the original article.