|
|
|
Pre-Requisites
This blog post assumes an Azure, AWS, GCP account is setup. The following links document paid or free tier:
| Azure [Microsoft] | AZ | PAID Tier Account | FREE Tier Account |
| Amazon Web Services | AWS | PAID Tier Account | FREE Tier Account |
| Google Cloud Platform | GCP | PAID Tier Account | FREE Tier Account |
Azure CLI
The Azure Command Line Interface is a set of commands used to create and manage Azure resources. The CLI is available across services designed to get working with Azure quickly with an emphasis on automation.
Linux
Install the Azure CLI on Linux | Choose an installation method e.g. apt (Ubunuty, Debian) | Launch Terminal
|
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash |
Mac OS/X
Install Azure CLI on Mac OS/X | Install with Homebrew | Install Homebrew manager if you haven't already!
|
brew update && brew install azure-cli |
Windows
Install Azure CLI on Windows | Microsoft Install (MSI) | Download the Latest MSI of the Azure CLI (64-bit)
|
Download and install https://aka.ms/installazurecliwindowsx64 |
After installing the Azure CLI on Linux, Mac OS/X, Windows confirm the current working version of the CLI:
|
az version |
AWS CLI
The AWS Command Line Interface is a unified tool used to manage your AWS services. Use the AWS CLI tool to download configure and control AWS services from the command line and automate them through scripts.
Linux
Install the AWS CLI on Linux | Linux tab | Command line installer - Linux x86 (64-bit) | Launch the Terminal
|
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install |
Mac OS/X
Install the AWS CLI on MacOS/X | macOS tab | GUI installer | Download the macOS pkg file AWSCLIV2.pkg
|
Download and install https://awscli.amazonaws.com/AWSCLIV2.pkg |
Windows
Install the AWS CLI on Windows | Windows tab | Download MSI | Download Windows (64-bit) AWSCLIV2.msi
|
Download and install https://awscli.amazonaws.com/AWSCLIV2.msi |
After installing the AWS CLI on Linux, Mac OS/X, Windows confirm the current working version of the CLI:
|
aws --version |
GCP CLI
The GCP Command Line Interface is used to create and manage Google Cloud resources + services directly from the command line and to perform common platform tasks faster by controlling cloud resources at scale.
Linux
Install the gcloud CLI | Linux tab | Platform Linux 64-bit (x86_64) | Launch Terminal + execute commands:
|
curl -O https://dl.google.com/dl/cloudsdk/channels/rapid/downloads/google-cloud-cli-linux-x86_64.tar.gz tar -xf google-cloud-cli-linux-x86_64.tar.gz | |
| cd google-cloud-sdk | ./install.sh |
Mac OS/X
Install the gcloud CLI | macOS tab | Platform macOS macOS 64-bit (ARM64, Apple silicon) | Launch Terminal
|
curl -O https://dl.google.com/dl/cloudsdk/channels/rapid/downloads/google-cloud-cli-darwin-arm.tar.gz tar -xf google-cloud-cli-darwin-arm.tar.gz | |
| cd google-cloud-sdk | ./install.sh |
Windows
Install the gcloud CLI | Windows tab | Download the Google Cloud CLI installer GoogleCloudSDKInstaller.exe
|
Download and install https://dl.google.com/dl/cloudsdk/channels/rapid/GoogleCloudSDKInstaller.exe |
After installing the gcloud CLI on Linux, Mac OS/X, Windows confirm the current working version of the CLI:
| gcloud init | gcloud version |
Master Key
Next, create master SSH key for secure, automated and controlled access to your Kubernetes infrastructure:
|
cd ~/.ssh ssh-keygen -t rsa -b 4096 -N '' -f master_ssh_key |
eval $(ssh-agent -s) ssh-add master_ssh_key |
Azure AKS
Microsoft provides Azure Kubernetes Services as fully managed Kubernetes container orchestration service. Follow all instructions below in order to provision a Kubernetes cluster and end-to-end test its functionality.
Download code sample here.
Pre-Requisites
az login |
Check Resources
az account list --output table az group list --output table az resource list --output table az resource list --query "[?location=='northeurope']" --output table az vm list --output table az aks list --output table az container list --output table az storage account list --output table az network public-ip list --output table |
Create Group
az group create --name stevepro-azraks-rg --location northeurope --debug |
Security Principal
az ad sp create-for-rbac --name ${USER}-sp --skip-assignment
|
Output
{
"appId": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"displayName": "stevepro-sp",
"password": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"tenant": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
}
|
Export
export AZ_SP_ID=<value_from_appId> export AZ_SP_PASSWORD=<value_from_password> |
Create Cluster
az aks create --name stevepro-azraks \
--resource-group stevepro-azraks-rg \
--dns-name-prefix stevepro-azraks \
--node-count 3 \
--node-vm-size Standard_D2s_v3 \
--kubernetes-version 1.31 \
--ssh-key-value ~/.ssh/master_ssh_key.pub \
--service-principal ${AZ_SP_ID} \
--client-secret ${AZ_SP_PASSWORD} \
--load-balancer-sku standard \
--network-plugin azure --debug
|
Get Credentials
export KUBECONFIG=~/.kube/config az aks get-credentials --name stevepro-azraks \ --resource-group stevepro-azraks-rg --file ~/.kube/config |
Deploy Test
kubectl create ns test-ns kubectl config set-context --current --namespace=test-ns kubectl apply -f Kubernetes.yaml kubectl port-forward service/flask-api-service 8080:80 curl http://localhost:8080 |
Output
Hello World (Python)! |
Shell into Node
mkdir -p ~/GitHub/luksa cd ~/GitHub/luksa git clone https://github.com/luksa/kubectl-plugins.git cd kubectl-plugins chmod +x kubectl-ssh kubectl get nodes ./kubectl-ssh node aks-nodepool1-20972701-vmss000000 |
Cleanup
kubectl delete -f Kubernetes.yaml kubectl delete ns test-ns |
Delete Cluster
az aks delete --name stevepro-azraks \ --resource-group stevepro-azraks-rg |
Delete Group
az group delete --name stevepro-azraks-rg --yes --no-wait az group delete --name NetworkWatcherRG --yes --no-wait |
Summary
To summarize, we have setup CLIs for Azure, Amazon and Google and provisioned an Azure AKS Kubernetes cluster with end-to-end testing. Next, we will resume to provision clusters for Amazon EKS and Google GKE. This will be the topic of the next post.
No comments:
Post a Comment