Deploy on Azure Using Helm Charts
Last updated
Was this helpful?
Last updated
Was this helpful?
Ensure the following tools are installed and configured:
1. Azure CLI
The Azure Command-Line Interface (CLI) is a cross-platform tool that allows you to manage Azure resources. To install please visit thedocumentation.
Before setting up AKS, you'll need to . Simply follow the on-screen instructions. Note that billing information will be required during the sign-up process.
2. kubectl
kubectl
is the command-line tool for interacting with Kubernetes clusters. To install kubectl
please refer to the .
3. Helm
Helm is a package manager for Kubernetes applications. To install please refer to .
Log In to Azure
Authenticate with your Azure account:
Follow the browser prompts to log in.
Create a Resource Group
Before provisioning your AKS cluster, create a resource group to organize and manage related resources.
Use the following command, replacing <resource-group-name>
with your desired name and <location>
with your preferred Azure region (e.g., eastus
):
Example:
This will create a new resource group named myAKSResourceGroup
in the eastus
region.
Enable the Microsoft.Compute Resource Provider
To use AKS, you must register the Microsoft.Compute
resource provider:
If the registration state shows "Registering"
, wait a few minutes for it to complete. You can check the current state with:
Proceed once the status returns "Registered"
.
Register the Operational Insights Resource Provider
To enable monitoring features in AKS, register the Microsoft.OperationalInsights
provider:
You can check the registration status with:
Wait until the status shows "Registered"
before proceeding.
Register the Microsoft.ContainerService Provider
Before creating your AKS cluster, you must register the Microsoft.ContainerService
resource provider, which is required to manage Kubernetes clusters in Azure.
Run the following command:
Then check the registration status:
Wait until the output returns:
Once it's registered, you can proceed with creating your AKS cluster.
Create an AKS Cluster
Create an AKS cluster with your specified parameters. Replace <resource-group-name>
with your resource group name, <cluster-name>
with your desired AKS cluster name, and adjust other parameters as needed:
For example:
Note: The --generate-ssh-keys
parameter will create SSH keys if they do not already exist.
Connect to the AKS Cluster
Once your AKS cluster is created, you can connect to it using kubectl
.
Retrieve the cluster credentials:
This command configures your local kubectl
context to interact with the AKS cluster:
Verify the connection:
Run the following to ensure you're connected and the node is active:
You should see an output similar to the one below. Make sure to note the Name of your node. You’ll need it in Part 2
You should see your AKS node listed in the output. If so, you're now connected and ready to deploy to your cluster!
Add the Hyperswitch Helm Repository
Update the repository to fetch the latest charts:
Prepare the Kubernetes Cluster
Label the Node for Hyperswitch:
Replace <node-name>
with the name of your node (use kubectl get nodes
to find it). We saved the name on Part I, Step 7.
For example:
Create a Namespace:
Namespaces help organize and isolate resources within your Kubernetes cluster. To create a new namespace, use the following command:
Example:
This creates a namespace called hyperswitch-dev
where you can deploy and manage related workloads separately from other environments.
Install Hyperswitch
Use Helm to deploy Hyperswitch into your Kubernetes cluster. Replace <release-name>
with your chosen release name and <namespace>
with the namespace you previously created:
Example:
This command installs the Hyperswitch stack into the specified namespace, allowing you to manage and upgrade the deployment easily through Helm.
Verify Installation
Check Pod Status:
Ensure all pods are in the Running
state:
Example:
Check Helm Release:
Example:
That's it! Hyperswitch should be up and running on your Azure account 🎉
Use the following command for port-forwarding to access the services. Replace <namespace>
with your namespace:
Access the services at:
Afterwards, you’ll be taken straight to the Control Center. If you're just taking things for a spin, feel free to skip authentication and start exploring right away.
Once you are done with the test payment, you can explore more about these:
Uninstall Hyperswitch:
Example:
helm uninstall hyperswitch -n hyperswitch
Delete the namespace:
kubectl delete namespace <namespace>
Example:
kubectl delete namespace hyperswitch
Delete the AKS cluster completely:
Example:
View Pod Logs:
To view logs for a specific pod:
View Events:
To view events in the namespace:
Reinstall Chart:
If issues persist, uninstall and reinstall Hyperswitch:
To customize Hyperswitch, clone the Helm chart repository and modify values.yaml
:
Update the values.yaml
file inside hyperswitch-stack/
and apply changes with:
App server:
Control center:
Hyperswitch Web:
Grafana:
Vector:
Mailhog:
The quickest way to explore Hyperswitch is via the . You can create an account or sign in with your email:
A magic link will be sent to . Click on the link in white:
Use can now use the Hyperswitch Control Center and .
Refer our to try out REST APIs.
How to set up routing rules
How to integrate Hyperswitch with your app
List of supported payment processors and payment methods
AI Powered observability to reduce cost