HiTechCloud ArgoCD Service Terms
PART I - PURPOSE AND SCOPE
Article 1. Purpose and scope of application
1.1. These Terms apply to the HiTechCloud ArgoCD service ("Service") — a solution for provisioning and managing Argo CD, built on the Argo CD open-source project from the Cloud Native Computing Foundation (CNCF), providing GitOps capability for deploying and synchronizing applications across Kubernetes clusters.
Article 2. Definitions
- “ArgoCD Instance” – a single ArgoCD deployment managed by HiTechCloud for the Customer;
- “Application” – the ArgoCD resource representing an application synchronized from Git to the target Cluster;
- “Project” – the organizational unit in ArgoCD used for permissions and policy;
- “Sync” – the act of reconciling the desired state (Git) with the actual state (cluster).
▸ Legal basis:
Civil Code 2015; Commercial Law 2005;
Law on Information Technology 2006; Law on Network Information Security 2015; Law on Cybersecurity 2018;
Decree 13/2023/ND-CP (PDPD); Decree 53/2022/ND-CP;
Decree 147/2024/ND-CP on the management of internet services.
PART II - SERVICE DESCRIPTION AND CONFIGURATION
Article 3. Service and product description
3.1. Services provided:
- Provisioning an ArgoCD instance in the Customer's environment (single-tenant) or multi-tenant via namespace;
- Connect to a Git repository (GitHub, GitLab, Bitbucket, on-prem) via SSH key or OAuth token;
- Declarative configuration through the App-of-Apps pattern or ApplicationSet;
- Supports Helm charts, Kustomize, Jsonnet and plain YAML; sync policies for auto-sync, manual, canary and blue-green via Argo Rollouts;
- Notification integrations (Slack, MS Teams, Email, Webhook) and Image Updater for automatic new-tag updates;
- ArgoCD configuration backup and fast rollback.
Article 4. Configurations, plans, and service levels
4.1. Service packages: Starter (1 ArgoCD instance, 50 applications); Pro (5 instances, 500 apps); Enterprise (unlimited, dedicated control plane, higher SLA).
4.2. Integrates with HKS and with clusters outside HiTechCloud via kubeconfig.
PART III - COMMITMENTS AND SUPPORT
Article 5. Service level agreement (SLA) and support
5.1. ArgoCD UI/API uptime ≥ 99.9%/month; sync engine reconcile lag < 60 seconds with 3-minute polling.
5.2. P1 response ≤ 30 minutes for Pro/Enterprise plans.
PART IV - RIGHTS AND OBLIGATIONS
Article 6. HiTechCloud's rights and obligations
- (a) Deploy and maintain the ArgoCD instance on a stable release;
- (b) Apply critical patches within 14 days of the upstream release;
- (c) Daily configuration backup with 30-day retention;
- (d) Granting RBAC permissions at the Customer's valid request.
Article 7. Customer's rights and obligations
- (a) Managing the Git repository, branch strategy and secrets;
- (b) Configure applications, projects and policies to your business requirements;
- (c) Secure Git and ArgoCD access and enable SSO and MFA;
- (d) Do not use the Service to run workloads that breach the AUP.
PART V - FEES AND PAYMENT
Article 8. Service fees and payment
8.1. Priced by plan + number of managed applications + Git cache capacity.
8.2. A surcharge applies when integrating with more than 5 clusters outside HiTechCloud.
PART VI - SECURITY AND COMPLIANCE
Article 9. Security, data, and legal compliance
9.1. Secrets in ArgoCD are integrated with Sealed Secrets and External Secrets (Vault, AWS Secrets Manager, GCP Secret Manager).
9.2. Every sync action and RBAC change is audit logged, with 12-month retention.
9.3. Complies with the CIS Kubernetes Benchmark and the Restricted Pod Security Standard.
PART VII - SUSPENSION, TERMINATION, AND EFFECT
Article 10. Suspension and termination
10.1. Suspension applies for resource abuse, AUP breach or overdue non-payment.
10.2. On termination: the Customer has 14 days to export the ArgoCD configuration (YAML manifests) before the instance is deleted.
Article 11. Effect and review
11.1. These terms take effect from 19/05/2026 and are reviewed in full at least once every 12 months, or whenever there is a material change in the law.
11.2. Any amendment or addition must be approved by the Director and published on the hitechcloud.vn service portal at least 15 days before it takes effect, except in an information security emergency.
11.3. These terms form an integral part of the Terms of Service and supplement the applicable policies. In the event of a conflict, the customer's specific appendices or order forms take precedence on scope and configuration; these terms take precedence on the SLA and on service-specific technical obligations.
