Exto
API Status
  • Introduction
  • Architecture
    • Microservice Architecture
    • Security
  • Release Cycle
  • Integration
    • Best Practices
    • Endpoints
    • Response Format
    • Error
    • Data Formats
    • Data API
      • Generate API Key
      • API
      • ID/Access Token
      • Azure API Gateway
      • Filter Master Record/Custom Module Records
  • Installation
    • Installing Exto on Kubernetes
      • Prerequisite
      • Installing Exto
        • Setup
        • Configuration
        • Installation
        • Purging
      • Tips and Tricks
        • AKS to use existing storage account
        • AKS with Application Gateway Ingress Controller
        • AKS Private Cluster
Powered by GitBook
On this page

Was this helpful?

  1. Installation
  2. Installing Exto on Kubernetes

Installing Exto

PreviousPrerequisiteNextSetup

Last updated 4 years ago

Was this helpful?

Recommendation

  • A minimum of two nodes are required and each node should be having at least 2 CPU, 8GB of memory to run Exto successfully.

  • Dev, QA, canary, prod Helm environments are already present. Please override values if needed. Or else you can start with a new environment for yourself if required and fill all the values from scratch.

  • All the resources follow ChartName-Namespace-Resource-Type naming convention. For Ex: exto-canary-api-svc which represents Exto chart's canary namespaced API service. You can't change the standard prefix ChartName-Namespace- for any kubernetes resource.

Setup
Configuration
Installation
Purging