Cloud Transformation

Container Platform on Huawei Cloud

Microservices on Cloud Container Engine, images through security gates into SWR, releases pulled in by Argo CD.

NGT's container platform design on Huawei Cloud. Code passes quality and image-scan gates before its image lands in SoftWare Repository for Container; Argo CD, running inside a private CCE cluster, pulls approved Helm releases from Git. Users reach the services through Web Application Firewall and Elastic Load Balance; data sits in RDS, Distributed Cache Service and Object Storage Service.

push imageapprovewatchsyncpull imageHTTPSCI · security gatesCD · GitOpsHuawei CloudRegional servicesVPCPublic subnetCCE cluster · private worker nodesData subnetDevelopment teamsmerge requestsGitLab CIbuild and unit testsSonarQubequality gateImage buildone Dockerfile per serviceTrivyimage scan gateHelm chartsconfig repoRelease approvalhigher environmentsUsersData EncryptionWorkshopkeys and secretsSoftWare Repositoryfor Container (SWR)Object StorageService (OBS)Web ApplicationFirewallElastic Load BalanceCloud ContainerEngine (CCE)managed KubernetesArgo CDGitOps syncMicroservicesone Helm release eachRDSPostgreSQL or MySQLDistributed CacheService (DCS)Redis

Point at a component to light its links; select it for what it does here and the practice that makes it right.

When to use it

  • New microservices built for Huawei Cloud
  • Applications re-platformed to containers during a migration
  • One delivery flow wanted on Huawei Cloud and on the other clouds

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation