Sustainability In Public Cloud

I am a big believer in?Sustainable Development?and try to contribute in my capacity. Earlier I wrote about how this archived in Private Cloud.

Sustainability In Private Cloud.

Today I will focus on how the same can be achieved in Public Cloud.

Of course, all the Public Cloud are doing their bit. Today I will focus on how as a Cloud Solution Architect we can do our bit at the application level.

ARM64 architecture is known for its high throughput and reduced energy consumption. It makes the Arm-based Processor a must for improving both the performance and the sustainability of Compute infra.

Azure has already made Arm-based virtual machine families GA and we can deploy our Arm based apps on the VM.

• Dpsv5 series: with up to 64 vCPUs and 4GiBs of memory per vCPU up to 208 GiBs,
• Dplsv5 series: with up to 64 vCPUs and 2GiBs of memory per vCPU up to 128 GiBs, and
• Epsv5 series: with up to 32 vCPUs and 8GiBs of memory per vCPU up to 208 GiBs.

As of today Arm-based workload can be only run on VM and it is not available on PaaS services like App Service. I am a big fan of PaaS Services, Let's see how we can run a Arm-based workload on AKS.

Steps to Deploy Arm-Based Pod on AKS.

• The first step is to create an Arm-based Container Image, to achieve the same use of a arm based tag e.g. 7.0-jammy-arm64v8 as below

FROM mcr.microsoft.com/dotnet/aspnet:7.0-jammy-arm64v8 AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM mcr.microsoft.com/dotnet/sdk:7.0 AS build
WORKDIR /src
COPY ["WebApplication1/WebApplication1.csproj", "WebApplication1/"]
RUN dotnet restore "WebApplication1/WebApplication1.csproj"
COPY . .
WORKDIR "/src/WebApplication1"
RUN dotnet build "WebApplication1.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "WebApplication1.csproj" -c Release -o /app/publish /p:UseAppHost=false

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "WebApplication1.dll"]        

• Add Arm-Based Node(Dpsv5 ) in your AKS Cluster
• Taint your node for your mixed workload type so that only arm-based images get deployed on the arm node.
• There will not be any impact in aks deployment file except the image tag and node selector.

PS: To build an Arm arm-based image you need Arm arm-based build agent or it will require a lot of configuration to build an arm64-based image on an amd64-based architecture.

The same Can be achieved on GKE GCP and AWS.

Source Code: som-nitjsr/sustianabilityonhyperscaler (github.com)

For a Better Future of the Next Generations