Frequently Asked Questions (FAQs)

You require the following permissions to create the Azure AKS resources:

The Azure account holder should have the role of a Global Administrator. The default role is User. As a Global Administrator you can create AKS clusters and other resources through the Azure Portal or the Azure CLI. Otherwise, the following error occurs:
Directory permission is needed for the current user to register the application.

For information about configuring the service principal portal, refer to Create service principal portal on Azure.
For more details, refer Check azure subscription permissions.

No. The available regions for the resource type - Microsoft.ContainerService/managedClusters are: eastus, westeurope, centralus, canadacentral, canadaeast.

No, you do not need an account with the Docker Hub to access the Quantum Fabric images. The images are public and you do not need any authorization to download them.

Yes, you can provide this as an input through the K8S_NODE_COUNT parameter in the aks_cluster_config.properties file along with the other parameters.

Yes, you can provide the custom address space by setting the value for VNET_ADDRESS_SPACE in the aks_cluster_config.properties file.

NOTE: To provide a custom address space, ensure that the AKS subnet address space, Azure application gateway subnet address space, and the jumpbox subnet address space, exist within the same virtual network address space and do not overlap.

Yes, you can provide an additional email address for alert notifications. To do so, you need to select the Azure role to configure sending alert notifications in the Azure portal. Perform the following steps:

1. Log in to the Azure portal.
2. Select Monitor, and then click Manage action groups.
3. Edit the action group for which the email IDs need to be added.
4. Select the role from the given list, as illustrated in the following image.

By default, for a window size of 60 minutes, polling will take place to check for threshold violation in every 5 minutes. A value for window size and polling time can be set on the Azure portal, if required.

NOTE: Based on the Azure subscription, user can customize the polling time according to requirement.

You can use the Azure DNS Service for installing Quantum Fabric.
For detailed documentation, refer to DNS-Getting Started Portal

You can whitelist the required IP addresses under the Firewall Rules of the Connection Security page for the Database, so that it is accessible by the DB user and the application.
For more details, refer to Firewall Rules

Yes, you can. Make sure that you maintain separate folders for each installation.

Go to the Resource Groups tab in the Azure portal and delete the resource group which was created during the installation.

If the error is related to some misconfiguration of the properties file, user permissions, or Azure quota issues, you need to fix those issues. Then you need to delete the resource group and execute the installation script.

You can have VNet Peering with the existing VNet created during the installation. Make sure that the address range for VNets does not overlap. The CIDR for the existing VNet is 10.0.0.0/8.

No, you cannot publish an app in WAR format. Quantum Fabric on Azure currently supports publishing an app only in Zip folder format. Publishing app in WAR format results in error.

No, you must first ensure that an installation is completed at least till the Application Gateway mapping and auto registration before running another setup in the same subscription. For a single subscription, do not run multiple installations parallelly even from 2 different client machines. This is very error prone and can end up in a state which is difficult to recover.

No, whenever a new installation needs to be done, you must extract a new folder from the installation zip. Do not try to reuse existing installation folder.

Command executed: kubectl get pods

Error Response: The connection to the server kony-a32c4f04.hcp.eastus.azmk8s.io:443 was refused - did you specify the right host or port?

Reason: The Kubernetes API server has been restricted to specific IPs. It is possible that you might be accessing the server from a machine whose IP is not authorized for the API.

server.

Validation: To check if the IP address of the machine from which you are accessing the API server is authorized, follow these steps.

1. Execute the following command:

   az aks show -n <AKS_cluster_name> -g <Resource_group_name>

2. From the output, check if your machine IP is listed in the authorizedIpRanges object in apiServerAccessProfile block.

If your machine IP is not listed there, then it does not have access to the API server and you cannot access the Kubernetes Server.

Resolution: To provide access to a machine IP which is not initially authorized, perform the following steps.

1. Execute the following command.

   az aks show -n <AKS_cluster_name> -g <Resource_group_name>

2. From the output, note the list of authorised IPs present in authorizedIpRanges object in the apiServerAccessProfile block.
3. Execute the following command by including the new machine IP in --api-server-authorized-ip-ranges parameter which is to be authorised in the following format.

   az aks update -g <Resource_group_name> -n 
   <AKS_cluster_name>--api-server-authorized-ip-ranges <existing_ip,existing_ip,…,new_ip>

After these steps are executed successfully, you can access the Kubernetes API server from your machine.