이 단계에서는 셸 환경을 설정하고 Apigee Hybrid 테스트에 적합한 Microsoft® Azure Kubernetes Service(AKS) 클러스터를 만드는 방법을 설명합니다.
터미널 셸 설정
로컬 셸에 Azure CLI(az) 및 kubectl이 설치되어 있는지 확인합니다. Azure CLI 도구는 Azure의 기본 명령줄 인터페이스를 제공하며 kubectl은 Kubernetes 클러스터를 대상으로 명령어를 실행할 수 있는 기본 명령줄 인터페이스를 제공합니다.
리소스 그룹 만들기
Azure 콘솔 또는 Azure CLI를 사용하여 리소스 그룹을 만듭니다. 예를 들면 다음과 같습니다.
az group create --name my-hybrid-rg --location eastus
모든 컨텍스트를 나열하여 현재 컨텍스트를 확인합니다. 다음 예시에서는 컨텍스트가 my-hybrid-aks-ext01로 설정됩니다.
kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO
my-hybrid-aks-cluster my-hybrid-aks-cluster clusterUser_my-hybrid-rg2_myhybrid-aks-cluster
* my-hybrid-aks-ext01 my-hybrid-aks-ext01 clusterUser_my-hybrid-rg_my-hybrid-aks-ext01
필요한 경우 현재 컨텍스트를 방금 만든 클러스터(Apigee Hybrid를 설치하려는 클러스터)로 설정합니다. 이전의 get-contexts 출력을 가정했을 때 만든 클러스터 이름이 my-hybrid-aks-cluster이면 다음과 같이 my-hybrid-aks-cluster 컨텍스트로 전환합니다.
kubectl config use-context my-hybrid-aks-cluster
여기서 my-hybrid-aks-cluster는 전환할 클러스터 컨텍스트의 이름입니다.
요약
이제 AKS에서 Kubernetes 클러스터를 실행했습니다. 셸 환경이 설정되었으며 이제 로컬 머신에 Apigee Hybrid 런타임 소프트웨어를 설치할 준비가 되었습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[[["\u003cp\u003eThis guide details how to set up a shell environment and create a Microsoft Azure Kubernetes Service (AKS) cluster suitable for testing Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eThe Azure CLI and \u003ccode\u003ekubectl\u003c/code\u003e tools are required and should be installed in your local shell for interacting with Azure and Kubernetes clusters.\u003c/p\u003e\n"],["\u003cp\u003eA resource group and a virtual network must be created within Azure, using the provided Azure CLI commands or through the Azure console.\u003c/p\u003e\n"],["\u003cp\u003eAn AKS cluster needs to be created, with specific configurations detailed in the provided table, ensuring that the node size is set to a minimum of DS3 Standard for sufficient CPU resources.\u003c/p\u003e\n"],["\u003cp\u003eThe current Kubernetes context must be set to the newly created AKS cluster to allow \u003ccode\u003ekubectl\u003c/code\u003e commands to interact with the correct cluster.\u003c/p\u003e\n"]]],[],null,["# Step 1: Create an AKS cluster\n\n| You are currently viewing version 1.1 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis step explains how to set up your shell environment and create a Microsoft®\nAzure Kubernetes Service\n(AKS) cluster suitable for testing Apigee hybrid.\n| There are many variations on how to create clusters in AKS. This topic walks through a basic scenario to help get you started with hybrid. For more detailed information about create clusters on AKS, see also [Quickstart:\n| Deploy an Azure Kubernetes Service cluster using the Azure CLI](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough) and [Quickstart: Deploy\n| an Azure Kubernetes Service (AKS) cluster using the Azure portal](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough)\n\nSet up your terminal shell\n--------------------------\n\nBe sure you have the [Azure CLI (az)](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest) and [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)\ninstalled in your local shell. The Azure CLI\ntool provides the primary command-line interface for Azure, and `kubectl` provides the primary\ncommand-line interface for running commands against Kubernetes clusters.\n\nCreate a resource group\n-----------------------\n\n\nCreate a resource group either using Azure console or with the Azure CLI. For example: \n\n```\naz group create --name my-hybrid-rg --location eastus\n```\n\nCreate a virtual network\n------------------------\n\n\nCreate a virtual network with a non-conflicting CIDR range. For example: \n\n```\naz network vnet create \\\n --name my-hybrid-rg-vnet \\\n --resource-group my-hybrid-rg \\\n --address-prefixes 120.38.1.0/24 \\\n --subnet-name my-hybrid-rg-vnet-subnet \\\n --subnet-prefix 120.38.1.0/26\n```\n\nCreate an AKS cluster\n---------------------\n\n| **Note:** Apigee does not support [GKE Sandbox](https://cloud.google.com/kubernetes-engine/sandbox) or [gVisor](https://github.com/google/gvisor).\n\n\nIn this step, you will create an AKS cluster.\n\n1. Open the [Microsoft® Azure Portal](https://portal.azure.com/).\n2. Click **Kubernetes services**.\n3. Create a cluster with the following minimum configuration settings. The configuration values shown below are for example purposes only. They are generally the default values and are suitable for testing purposes. It is up to you to decide how to configure your cluster to suit your requirements.\n\n4. Click **Review and Create**.\n5. When the cluster creation completes, go to the next step.\n\nSet cluster credentials\n-----------------------\n\n\nAdd the kubernetes cluster credentials for the newly created cluster using the following command\nif not already added. For example: \n\n```\naz aks get-credentials --resource-group my-hybrid-rg --name my-hybrid-aks-cluster\n```\n\nSet the current context\n-----------------------\n\n\nA *context* is a group of access parameters. Each context contains a Kubernetes cluster,\na user and a namespace. The current context is the cluster that is currently the default for\n`kubectl`: all `kubectl` commands run against that cluster.\n\n\nMake sure the current context is set to the cluster you just created. For example: \n\n```\nkubectl config current-context\n my-hybrid-aks-cluster-context\n```\n\n\nIf the context is not set to your cluster as expected, follow these steps to change it:\n\n1. List all the contexts to determine which is the *current* context. In the following example, the context is set to the `my-hybrid-aks-ext01`: \n\n ```\n kubectl config get-contexts\n CURRENT NAME CLUSTER AUTHINFO\n my-hybrid-aks-cluster my-hybrid-aks-cluster clusterUser_my-hybrid-rg2_myhybrid-aks-cluster\n * my-hybrid-aks-ext01 my-hybrid-aks-ext01 clusterUser_my-hybrid-rg_my-hybrid-aks-ext01\n\n ```\n2. If necessary, set the current context to the cluster you just created (the cluster into which you intend to install Apigee hybrid). Assuming the previous `get-contexts` output, if the cluster name you created were `my-hybrid-aks-cluster`, you would switch to the `my-hybrid-aks-cluster` context, as follows: \n\n ```\n kubectl config use-context my-hybrid-aks-cluster\n ```\n\n Where `my-hybrid-aks-cluster` is the name of the cluster context to switch to.\n\nSummary\n-------\n\n\nYou now have a Kubernetes cluster running in AKS. Your shell environment is\nset up, and you are ready to install the Apigee hybrid runtime software\non your local machine.\n[1](/apigee/docs/hybrid/v1.1/install-create-cluster-aks) [(NEXT) Step 2: Install apigeectl](/apigee/docs/hybrid/v1.1/install-download-install-aks) [3](/apigee/docs/hybrid/v1.1/install-copy-overrides-aks) [4](/apigee/docs/hybrid/v1.1/install-apply-hybrid-aks)\n\n\u003cbr /\u003e"]]
