Cluster resources created using the Azure Marketplace are preconfigured to use various namespaces. In most cases, when running
kubectl commands referenced in the documentation, remember to include the
-n insights argument, to make sure all resources under "insights" namespace appear, as well.
The Azure Marketplace deployment experience is tailored to a DevOps or System Engineer persona. Only use the Advanced Settings section if you understand your system needs. Our Support team are available to assist you if you have any questions.
Before installing kdb Insights Enterprise on Azure, you need the following:
Please refer to the Permissions Guidelines.
Ensure that you choose an Azure Region with availability zones.
By default, the kdb Insights Enterprise deployment will run across 3 Availability Zones (AZ) for higher resilience. The Reliable Transport component (RT) will run across 3 different nodes but each node is not set to run in each AZ due to performance considerations. If you want each RT to run in a different AZ to ensure maximum resiliency, you can set the service affinity configuration.
The deployment requires one public IP address used for Ingress.
If you define an assembly ingesting data published from outside of the cluster, using an kdb Insights Stream (Reliable Transport), each assembly requires three additional public IPs.
Required Resource Providers:
The Resource Providers listed below must be registered in the subscription; if you are missing any of them, your deployment can fail.
To learn how to register resource providers, follow Microsoft Guidance.
Required Resource Providers Microsoft.Compute Microsoft.ContainerService Microsoft.Network Microsoft.OperationsManagement Microsoft.OperationalInsights Microsoft.Insights Microsoft.Resources Microsoft.ManagedIdentity Microsoft.Authorization Microsoft.Solutions
Private AKS Cluster
Please be aware that kdb Insights Enterprise on Azure Marketplace does not support Private AKS Clusters or air-gapped environments at this time.