Microsoft frequently updates the version of AKS based on new features that are available in the Kubernetes platform.

In future releases, this upgrade will be available for customers to install.

DuploCloud provides a way to connect directly to the Cluster namespace using the kubectl token.

See kubectl Setup for available options.

Organization of use cases

Topics in this section are covered in the order of typical usage. Use cases that are foundational to DuploCloud such as Infrastructure, Tenant, and Hosts are listed at the beginning of this section; while supporting use cases such as Logs, Metrics, and Faults and alerts appear near the end.

Supported use cases for DuploCloud Azure

Secure your Azure cloud data by enabling for data at rest, using Encryption Key Management. Configuring this feature for your DuploCloud Infrastructure enables you to specify customer-managed keys or customer-provided keys for your existing Blob storage.

Configuring Azure encrypted storage accounts in DuploCloud

1. In the DuploCloud Portal, navigate to Administrator

Creating an Infrastructure

In DuploCloud, an maps one-to-one to a VPC in a specified region. It also maps to an cluster for container orchestration. Up to one instance (0 or 1) of an AKS is supported for each DuploCloud Infrastructure.

1. Select Administrator -> Infrastructure from the navigation menu.

Once your Infrastructure and Plan have been created, the final step before creating a Tenant is to enable Azure Kubernetes Service (AKS) to connect with Azure cloud management.

Enabling the AKS Kubernetes Cluster

1. In the DuploCloud Portal, navigate to Administrator -> Infrastructure.

In Azure, Microsoft cloud features such as Azure resource groups, Azure managed identity, Azure application security groups (ASG), KMS keys, and Kubernetes Namespaces are exposed in Tenants which reference their configurations.

For more information about DuploCloud Tenants, see the topic in the Getting Started with DuploCloud section.

Creating a Tenant

1. Navigate to Administrator

Managing Tenant Expiration

In the DuploCloud Portal, configure an expiration time for a Tenant. At the set expiration time, the Tenant and associated resources are deleted.

1. In the DuploCloud Portal, navigate to Administrator -> Tenants. The Tenants page displays.

2. From the Name column, select the Tenant for which you want to configure an expiration time.
3. From the Actions list box, select Set Tenant Expiration. The Tenant - Set Tenant Expiration pane displays.
4. Select the date and time (using your local time zone) when you want the Tenant to expire.

5. Click Set. At the configured day and time, the Tenant and associated resources will be deleted.

The DuploCloud Portal allows you to view and manage cloud resource usage costs. As an administrator, you can view your organization’s billing data by month, week, or Tenant. Non-administrator users can access billing data for Tenants they have permission to view. You can also configure billing alerts, analyze historical usage trends, and view DuploCloud license usage.

DuploCloud provides centralized logging and observability features that help you monitor AWS services, tenants, and individual applications.

Standard Observability Logs View tenant-scoped or system-wide logs using OpenSearch or Kibana dashboards:

• Observability -> Standard -> Logging

• Administrator -> Observability -> Standard -> Logging

See Standard Observability Logs documentation.

Advanced Observability Suite (AOS) Logs Access enhanced Grafana dashboards with live logs, traces, and detailed queries:

• Observability -> Advanced -> Dashboard -> Logs

• Administrator -> Observability -> Advanced -> Dashboard -> Logs

See documentation.

Container Logs For Kubernetes workloads, view logs per container:

See the Azure documentation.

In addition to the visibility of faults in the UI, DuploCloud also supports sending these notifications to the following systems:

• Sentry

• PagerDuty

• NewRelic

• AWS WorkDocs

• OpsGenie

Refer to the link for the detailed configuration.

Azure Availability Sets enhance the high availability and fault tolerance of virtual machines (VMs) deployed within Azure. They distribute VMs across multiple fault and update domains to protect against hardware failures and reduce downtime during maintenance events.

In DuploCloud, Availability Sets can be configured when creating or managing hosts. There are two types of Availability Sets:

• Aligned Availability Set: Used for VMs with managed disks and provides better fault domain management.

• Classic Availability Set: Used for VMs with unmanaged disks and follows older Azure infrastructure standards.

Create Virtual Machine (VM) snapshots in the DuploCloud Portal.

Creating a Virtual Machine(VM) Host Snapshot

1. In the DuploCloud Portal, navigate to Cloud Services -> Hosts. The Hosts page displays.

DuploCloud supports various ways to scale the workload, depending on the underlying Azure services being used.

When you use autoscaling for Azure agent pools, you allow DuploCloud to manage your application's capacity requirements within your limits.

Creating an autoscaled Azure agent pool

In the DuploCloud Portal, with the Enable Autoscaling option selected. Each agent pool contains nodes backed by the virtual host machines.

Metrics of the resources created/managed in DuploCloud can be tracked under Observability -> Metrics.

Separate tabs are available to view the metrics resource type wise.

Configuring Tenant Config settings

You can configure settings to apply to all new Tenants under a Plan using the Config tab. Tenant Config settings will not apply to Tenants created under the Plan before the settings were configured.

1. From the DuploCloud portal, navigate to Administrator -> Plan.

To enable the billing feature in DuploCloud for Microsoft Azure, you must assign the Billing Reader role to the DuploCloud master VM (DuploMaster), restart the VM to apply the change, verify that the billing service is running, and then enable billing in the DuploCloud Portal.

Step 1. Assign the Billing Reader Role

Follow the Azure documentation to .

When assigning the role:

Creating a direct link to the Azure Portal from your DuploCloud Infrastructure saves your time when you work with DuploCloud Azure resources. Instead of toggling between the DuploCloud Portal and the Microsoft Azure Portal, get instant access to the Azure Portal from DuploCloud.

Creating a link to the Azure Portal

1. In the DuploCloud Portal, navigate to Administrator -> Infrastructure. The Infrastructure page displays.

2. From the Name column, select the Infrastructure for which you want to add a link to the Azure Console.

3. Click the Metadata tab.

Accessing the Azure Portal

After you to an Infrastructure, access the Azure Console from the DuploCloud Portal in the Actions menu for Azure Hosts.

1. In the DuploCloud Portal, navigate to Cloud Services -> Hosts. The Hosts page displays.

2. From the Name column, select the Host you are working with.

3. From the Actions menu, select Connect -> Azure Portal.

Usage costs for resources can be viewed and managed in the DuploCloud Portal, by month or week, and by Tenant. You can also explore historical resource costs.

Prerequisites

• Complete the steps on the Enable GCP billing data page before attempting to view billing data in the portal.

Viewing Azure Billing Data

1. In the DuploCloud Portal, naviagate to Administrator -> Billing.

You can view usage by:

• Time

  • Select the Spend by Month tab and click More Details to display monthly and weekly spending options.

• Tenant

Setting Up Billing Alerts

To monitor cloud costs based on usage, you can configure Billing Alerts in DuploCloud. For more details, see the .

Shared Hosts allow workloads to run on the same set of virtual machines (VMs), making better use of resources across multiple Tenants. DuploCloud supports Services, Jobs, and CronJobs on Shared Hosts in Azure, providing flexibility for running long-running services, batch jobs, and scheduled tasks.

DuploCloud supports Shared Hosts for:

• Services

• Jobs

• CronJobs

Introduction

Faults that happen in the system be it Infrastructure creation, Container deployments, or Application health checks can be tracked in the DuploCloud portal under Faults Menu.

Once we have the Infrastructure (Networking, Kubernetes cluster, and other common configurations) and an environment (Tenant) set up, the next step is to create VMs. In DuploCloud, you can create the following types of hosts for your workloads:

• Host (VM): Standard virtual machines for general-purpose workloads, including application hosting and databases.

• VM Scale Set: A group of identical VMs that can automatically scale based on demand, ideal for horizontally scalable applications.

• Azure Agent Pool: A set of VMs used in container orchestration environments like Azure Kubernetes Service (AKS).

• Availability Set: A collection of VMs spread across fault and update domains to ensure high availability and minimize downtime.

• BYOH (Bring Your Own Host): For users with pre-configured VMs or non-Azure infrastructure that they want to bring into DuploCloud. Use BYOH for any VM that is not an Azure Host.

Adding Hosts in DuploCloud

Adding a Host (VM)

1. Select the appropriate Tenant from the Tenant list box.

2. Navigate to Cloud Services -> Hosts.

3. Select the Host tab.

4. Click

1. In the Friendly Name field, specify a unique name for the Host.

2. Define the Subnet for the Host.

3. Select the Instance Type that fits your requirements.

4. Enter the Username and Password for the Host.

Adding a VM Scale Set

1. Select the appropriate Tenant from the Tenant list box.

2. Navigate to Cloud Services → Hosts.

3. Select the VM Scale Set tab.

4. Click Add. The Add VM Scale Set pane displays.

Adding an Azure Agent Pool

1. Select the appropriate Tenant from the Tenant list box.

2. Navigate to Cloud Services → Hosts.

3. Select the Azure Agent Pool tab.

4. Click Add. The Add Azure Agent Pool pane displays.

Adding an Azure Availability Set

For detailed instructions, see the .

Adding a BYOH (Bring Your Own Host)

1. Select the appropriate Tenant from the Tenant list box.

2. Navigate to Cloud Services → Hosts.

3. Select the BYOH tab.

4. Click Add. The Add BYOH pane displays.

Viewing Hosts (VMs)

To view your Hosts (VMs), navigate to Cloud Services -> Hosts and select the Host tab.

Creating Kubernetes StorageClass and PVC constructs in the DuploCloud Portal.

See .

Host abstraction and isolation

While lower-level details such as IAM roles and security groups are abstracted, deriving instead from the Tenant, only the most application-centric inputs are required to set up Hosts.

Most of these inputs are optional and some are available as list box selections, set by the administrator in the Plan (for example, Image ID, in Host Advanced Options).

There are two additional parameters

Fleet: This is applicable if the VM is to be used as a host for by the platform. The choices are:

• Linux Docker/Native: To be used for hosting Linux containers using the .

• Docker Windows: To be used for hosting Windows containers using the .

• None: To be used for non-Container Orchestration purposes and contents inside the VM are self-managed by the user.

Allocation Tags (Optional): If the VM is used for containers, you can optionally set a label on the VM. This label is specified during Docker application deployment to ensure that the application containers are pinned to a specific set of nodes, giving you the ability to split a tenant further into separate pools of servers and deploy applications on them.