70
CHAPTER 3 | Architecting container and microservice-based applications
Figure 4-25. Running Kubernetes in dev machine and the cloud
Getting started with Azure Kubernetes Service (AKS)
To begin using AKS, you deploy an AKS cluster from the Azure portal or by using the CLI. For more
information on deploying a Kubernetes
cluster in Azure, see
Deploy an Azure Kubernetes Service
(AKS) cluster
.
There are no fees for any of the software installed by default as part of AKS. All default options are
implemented with open-source software. AKS is available for multiple virtual machines in Azure.
You’re charged only for the compute instances
you choose, and the other underlying infrastructure
resources consumed, such as storage and networking. There are no incremental charges for AKS itself.
The default production deployment option for Kubernetes is to use Helm charts, which are introduced
in the next section.
Deploy with Helm charts into Kubernetes clusters
When deploying an application to a
Kubernetes cluster, you can use the original kubectl.exe CLI tool
using deployment files based on the native format (.yaml files), as already mentioned in the previous
section. However, for more complex Kubernetes applications such as when deploying complex
microservice-
based applications, it’s
recommended to use
Helm
.
Helm Charts helps you define, version, install, share, upgrade, or rollback even the most complex
Kubernetes application.
Going further, Helm usage is also recommended because other Kubernetes environments in Azure,
such as
Azure Dev Spaces
are also based on Helm charts.
Helm is maintained by the
Cloud Native Computing Foundation (CNCF)
- in
collaboration with
Microsoft, Google, Bitnami, and the Helm contributor community.
71
CHAPTER 3 | Architecting container and microservice-based applications
For more implementation information on Helm charts and Kubernetes, see the
Using Helm Charts to
deploy
eShopOnContainers to AKS
post.
Dostları ilə paylaş: