Questo passaggio spiega come configurare l'ambiente shell e creare un cluster Microsoft®
Azure Kubernetes Service
(AKS) adatto per testare Apigee hybrid.
Configura la shell del terminale
Assicurati di avere installato lo strumento
Azure CLI (az) e kubectl
nella shell locale. Lo strumento Azure CLI fornisce l'interfaccia a riga di comando principale per Azure, mentre kubectl fornisce l'interfaccia a riga di comando principale per l'esecuzione di comandi sui cluster Kubernetes.
Creare un gruppo di risorse
Crea un gruppo di risorse utilizzando la console di Azure o Azure CLI con il seguente comando:
az group create --name my-hybrid-rg --location eastus
Crea una rete virtuale
Crea una rete virtuale con un intervallo CIDR non in conflitto.
Crea un cluster con le seguenti impostazioni di configurazione minime.
Spazio di archiviazione minimo consigliato: esamina le specifiche del disco AKS e scegli una dimensione del volume di archiviazione in base alle tue esigenze di IOPS e costi.
La regione specificata in precedenza. Ad esempio: (US) East US
Nome del cluster Kubernetes
Il nome del cluster. Ad esempio: my-hybrid-aks-cluster
Versione di Kubernetes
Scegli la versione 1.16.x o una versione successiva
Prefisso del nome DNS
Il prefisso del nome DNS. Ad esempio: my-hybrid-aks-cluster-dns
Conteggio nodi
3
Dimensione del nodo
DS3 Standard
Scala
Nodi virtuali
Disabilitato
Set di scalabilità di VM
Abilitato
Autenticazione
Abilita RBAC
Sì
Entità servizio
Predefinito
Networking
Routing delle applicazioni HTTP
No
Bilanciatore del carico
Standard
Configurazione di rete
Azure CNI
Rete virtuale
Il nome della rete virtuale. Puoi selezionare la rete virtuale creata
in precedenza o crearne una nuova facendo clic sul link Crea nuova. Ad esempio: my-hybrid-rg-vnet
Subnet del cluster
Esempio: default (10.240.0.0/16)
Intervallo di indirizzi dei servizi Kubernetes
L'intervallo di indirizzi dei servizi. Assicurati di utilizzare un intervallo di indirizzi non in concorrenza.
Ad esempio: 10.0.0.0/16
Indirizzo IP del servizio DNS di Kubernetes
Ad esempio: 10.0.0.10
Indirizzo della bridge Docker
Ad esempio: 172.17.0.1/16
Monitoraggio
Abilita il monitoraggio dei container
Sì
Spazio di lavoro Log Analytics
Ad esempio: DefaultWorkspace-66f9d75c-2cd9-47dd-ad0f-c43d888e9cef-EUS
Tag
Nessuno
Fai clic su Esamina e crea.
Al termine della creazione del cluster, vai al passaggio successivo.
Imposta le credenziali del cluster
Aggiungi le credenziali del cluster Kubernetes per il cluster appena creato utilizzando il seguente comando se non sono già state aggiunte:
az aks get-credentials --resource-group my-hybrid-rg --name my-hybrid-aks-cluster
Impostare il contesto corrente
Un contesto è un gruppo di parametri di accesso. Ogni contesto contiene un cluster Kubernetes, un utente e uno spazio dei nomi. Il contesto corrente è il cluster attualmente predefinito per kubectl: tutti i comandi kubectl vengono eseguiti su quel cluster.
Assicurati che il contesto corrente sia impostato sul cluster appena creato utilizzando il seguente comando:
Se il contesto non è impostato sul cluster come previsto, segui questi passaggi per modificarlo:
Elenca tutti i contesti per determinare quale sia il contesto corrente. Nel
seguente esempio, il contesto è impostato su 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
Se necessario, imposta il contesto corrente sul cluster appena creato (il cluster
in cui intendi installare Apigee hybrid). Supponendo l'output get-contexts precedente,
se il nome del cluster che hai creato fosse my-hybrid-aks-cluster, passeresti al
contesto my-hybrid-aks-cluster, come segue:
kubectl config use-context my-hybrid-aks-cluster
dove my-hybrid-aks-cluster è il nome del contesto del cluster a cui passare.
Riepilogo
Ora hai un cluster Kubernetes in esecuzione in AKS. L'ambiente shell è stato configurato e puoi installare il software di runtime ibrido Apigee sulla tua macchina locale.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eThis documentation is for Apigee hybrid version 1.3, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eThe guide provides instructions for setting up a shell environment and creating a Microsoft Azure Kubernetes Service (AKS) cluster for testing Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eUsers are instructed to install the Azure CLI (az) and kubectl tools in their local shell for interacting with Azure and Kubernetes.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation outlines how to create a resource group and virtual network within Azure, including defining address ranges and subnet specifications.\u003c/p\u003e\n"],["\u003cp\u003eThe guide details the process of creating an AKS cluster with recommended minimum configuration settings, including node size, Kubernetes version, networking, and monitoring configurations, suitable for testing purposes.\u003c/p\u003e\n"]]],[],null,["# Step 1: Create a cluster\n\n| You are currently viewing version 1.3 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| **Upgrading:** If you are upgrading to Apigee hybrid v1.3.0, see [Upgrading Apigee hybrid](/apigee/docs/hybrid/v1.3/upgrade) for instructions. If you are performing a new installation, continue with the configurations described below.\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| **Note:** 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 creating clusters on AKS, see [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/)\ntool installed 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 using the following command: \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.\n\n\nFor example: \n\n### Syntax\n\n```\naz network vnet create \\\n --name vnet-name \\\n --resource-group my-hybrid-rg \\\n --address-prefixes vnet-address-range \\\n --subnet-name vnet-subnet-name \\\n --subnet-prefix subnet-address-range\n```\n\n### 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/14 \\\n --subnet-name my-hybrid-rg-vnet-subnet \\\n --subnet-prefix 120.38.1.0/16\n```\n\n\nWhere:\n\n1. \u003cvar translate=\"no\"\u003emy-hybrid-rg\u003c/var\u003e is the name of the virtual network.\n2. \u003cvar translate=\"no\"\u003evnet-address-range\u003c/var\u003e is a list of address blocks reserved for this virtual network in CIDR notation.\n3. \u003cvar translate=\"no\"\u003evnet-subnet-name\u003c/var\u003e is the name of the subnet within the virtual network.\n4. \u003cvar translate=\"no\"\u003esubnet-address-range\u003c/var\u003e is a list of address blocks reserved for this subnet in CIDR notation.\n\nCreate an AKS cluster\n---------------------\n\n| **Caution:** Apigee does not support [GKE Sandbox](https://cloud.google.com/kubernetes-engine/docs/concepts/sandbox-pods) 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. **Note:** 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\n\n **Recommended minimum storage**: Review the AKS disk specifications and choose a storage volume size\n based on your IOPs and cost requirements.\n\n\n You can see cluster configuration guidelines for Apigee hybrid in\n [Configure Cassandra for production](/apigee/docs/hybrid/v1.3/cassandra-production) and\n [StorageClass configuration](/apigee/docs/hybrid/v1.3/cassandra-config).\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: \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 using the following command: \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.3/install-create-cluster-aks) [(NEXT) Step 2: Install cert-manager and ASM](/apigee/docs/hybrid/v1.3/install-download-cert-manager-istio-aks) [3](/apigee/docs/hybrid/v1.3/install-download-install-aks) [4](/apigee/docs/hybrid/v1.3/install-copy-overrides-aks) [5](/apigee/docs/hybrid/v1.3/install-apply-hybrid-aks)\n\n\u003cbr /\u003e"]]
