Cloud SDK를 설치한 후 다음 명령어를 실행하여 kubectl 명령줄 도구를 설치합니다.
gcloud components install kubectl
gcloud 도구를 사용하여 기본 프로젝트와 컴퓨팅 리전 등 두 가지 기본 설정을 구성합니다.
gcloud를 사용하려면 작업할 프로젝트와 컴퓨팅 영역을 지정해야 하므로 이러한 설정을 구성하면 gcloud 명령어를 더욱 쉽게 실행할 수 있습니다.
현재 설정을 나열하려면 다음 단계를 따르세요.
gcloud config list
프로젝트 또는 컴퓨팅 영역이 나열되지 않으면 아래 표시된 명령어를 사용하여 추가해야 합니다. 목록 출력에서 프로젝트 및 컴퓨팅 리전(또는 영역)을 반영하도록 현재 설정을 전환해야 한다고 판단되는 경우 다음 명령어를 사용할 수 있습니다.
gcloud config set project project-idgcloud config set compute/region compute-regiongcloud config set compute/zone compute-zone
여기에서 project-id는 GCP 프로젝트의 이름이고 compute-region은 GCP 컴퓨팅 리전의 이름이고 compute-zone은 GCP 컴퓨팅 영역의 이름입니다. 예를 들면 compute/region us-central1입니다. 컴퓨팅 리전 및 영역 목록은 사용 가능한 리전 및 영역을 참조하세요.
클러스터를 만드는 데 몇 분 정도 걸릴 수 있습니다. 성공하면 RUNNING 상태와 비슷한 출력이 표시됩니다.
NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
apigee-hybrid us-central1-a 1.13.11-gke.9 35.222.54.89 n1-standard-4 1.13.11-gke.9 3 RUNNING
현재 컨텍스트 설정
컨텍스트는 액세스 매개변수 그룹입니다. 각 컨텍스트에는 Kubernetes 클러스터, 사용자, 네임스페이스가 포함되어 있습니다. 현재 컨텍스트는 현재 kubectl의 기본값인 클러스터입니다. 모든 kubectl 명령어가 이 클러스터를 대상으로 실행됩니다.
현재 gcloud 컨텍스트가 방금 만든 클러스터로 설정되어 있는지 확인합니다.
먼저 컨텍스트를 나열하여 컨텍스트가 현재 컨텍스트인지 확인합니다. 다음 예시에서 현재 컨텍스트는 gke_hybrid-project_us-central1-a_apigee-hybrid입니다.
이름에는 GCP 프로젝트 이름(hybrid-project), 리전 또는 영역(us-central1-a), 클러스터 이름(apigee-hybrid)이 포함됩니다.
kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
* gke_hybrid-project_us-central1-a_apigee-hybrid gke_hybrid-project_us-central1-a_apigee-hybrid gke_hybrid-project_us-central1-a_apigee-hybrid
gke_apigee-project_us-west1-a_apigee-cluster gke_apigee-project_us-west1-a_apigee-cluster gke_apigee-project_us-west1-a_apigee-cluster
필요한 경우 현재 컨텍스트를 방금 만든 클러스터(Apigee Hybrid를 설치하려는 클러스터)로 설정합니다. 이전 get-contexts 출력을 추정하고 만든 클러스터 이름이 us-west1 리전에서 apigee-cluster이면 gke_apigee-project_us-west1-a_apigee-cluster 컨텍스트로 전환할 것입니다.
[[["이해하기 쉬움","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 provides instructions for setting up a shell environment and creating a Google Kubernetes Engine (GKE) cluster in a Google Cloud Platform (GCP) project, which is required for a trial Apigee hybrid installation.\u003c/p\u003e\n"],["\u003cp\u003eUsers must ensure they have both the \u003ccode\u003egcloud\u003c/code\u003e and \u003ccode\u003ekubectl\u003c/code\u003e command-line tools installed and configured, including setting the default project and compute region or zone using the \u003ccode\u003egcloud config\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eA GKE cluster is created using the \u003ccode\u003egcloud container clusters create\u003c/code\u003e command, and the guide provides settings to create a minimally configured cluster suitable for a trial installation, while also warning that Apigee does not support GKE Sandbox or gVisor.\u003c/p\u003e\n"],["\u003cp\u003eAfter cluster creation, the current context for \u003ccode\u003ekubectl\u003c/code\u003e commands must be set to the newly created cluster to ensure that all subsequent commands are executed against it, using \u003ccode\u003ekubectl config use-context\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eFinally, the guide explains how to fetch cluster credentials using \u003ccode\u003egcloud container clusters get-credentials\u003c/code\u003e and how to grant the cluster-admin role to the user with \u003ccode\u003ekubectl create clusterrolebinding\u003c/code\u003e, in order to have the adequate access to the cluster.\u003c/p\u003e\n"]]],[],null,["# Step 1: Create a GKE 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 GKE cluster\nin your Google Cloud Platform (GCP) project.\n\nSet up your terminal shell\n--------------------------\n\nThe `gcloud` tool provides the primary command-line interface\nfor GCP, and `kubectl` provides the primary command-line interface for\nrunning commands against Kubernetes clusters.\n\n1. Be sure you have `gcloud` and `kubectl` installed in your\n local shell. The `gcloud` tool provides the primary command-line interface\n for GCP, and `kubectl` provides the primary command-line interface for\n running commands against Kubernetes clusters.\n\n gcloud -h\n kubectl -h\n\n2. If you do not have these utilities installed, install them now:\n 1. [Install the Cloud SDK](https://cloud.google.com/sdk/install), which includes the `gcloud` command-line tool.\n 2. After installing Cloud SDK, install the `kubectl` command-line tool by running the following command: \n\n ```\n gcloud components install kubectl\n ```\n3. Use the `gcloud` tool to configure two default settings: your default [project](https://cloud.google.com/resource-manager/docs/creating-managing-projects) and [compute region](https://cloud.google.com/compute/docs/regions-zones/#available). Configuring these settings makes it easier to run `gcloud` commands, because `gcloud` requires that you specify the project and compute zone in which you want to work.\n\n\n To list the current settings: \n\n ```\n gcloud config list\n ```\n\n\n If a project and/or compute zone is not listed, then you need to add them with the\n commands shown below. If, from the list output, you determine that you need to switch the current settings\n to reflect your project and compute region (or zone), you can also use these commands: \n\n gcloud config set project \u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e\n gcloud config set compute/region \u003cvar translate=\"no\"\u003ecompute-region\u003c/var\u003e\n gcloud config set compute/zone \u003cvar translate=\"no\"\u003ecompute-zone\u003c/var\u003e\n\n\n Where \u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e is the name of your GCP project, \u003cvar translate=\"no\"\u003ecompute-region\u003c/var\u003e is\n the name of a GCP compute region, and \u003cvar translate=\"no\"\u003ecompute-zone\u003c/var\u003e is\n the name of a GCP compute zone. For example: `compute/region us-central1`. For a list of\n compute regions and zones, see [Available regions and zones](https://cloud.google.com/compute/docs/regions-zones/#available).\n\nCreate a GKE 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 a Kubernetes cluster in your GCP project (the project you set\nwith the `gcloud config` command).\n| **NOTE:** The following command assumes you set the `gcloud` configuration for the compute region and/or zone, as explained in the previous steps. If you did not set the configuration, then you will need to add the `--region \"`\u003cvar translate=\"no\"\u003ecompute-region\u003c/var\u003e`\"` and/or `--zone \"`\u003cvar translate=\"no\"\u003ecompute-zone\u003c/var\u003e`\"` parameter to the command.\n\n\nExecute the following command to create the cluster. The machine type, number of nodes, and\nother settings specified in the command create a minimally configured cluster suitable for\na trial Apigee hybrid installation: \n\n```\ngcloud container clusters create cluster-name \\\n--machine-type \"n1-standard-4\" --num-nodes \"3\" --enable-autoscaling --min-nodes \"3\" --max-nodes \"6\"\n```\n\n\nWhere \u003cvar translate=\"no\"\u003ecluster-name\u003c/var\u003e is the name you choose for the cluster.\n\n\nCluster creation can take a few minutes. Upon success, you will see output similar to\nthe following with a status of `RUNNING`: \n\n```\nNAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS\napigee-hybrid us-central1-a 1.13.11-gke.9 35.222.54.89 n1-standard-4 1.13.11-gke.9 3 RUNNING\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 `gcloud` context is set to the cluster you just created.\n\n1. First, list the contexts to determine which is the *current* context. In the following example, the current context is `gke_hybrid-project_us-central1-a_apigee-hybrid`. The name includes the name of a GCP project (`hybrid-project`), a region or zone (`us-central1-a`), and a cluster name (`apigee-hybrid`): \n\n ```\n kubectl config get-contexts\n CURRENT NAME CLUSTER AUTHINFO NAMESPACE\n * gke_hybrid-project_us-central1-a_apigee-hybrid gke_hybrid-project_us-central1-a_apigee-hybrid gke_hybrid-project_us-central1-a_apigee-hybrid\n gke_apigee-project_us-west1-a_apigee-cluster gke_apigee-project_us-west1-a_apigee-cluster gke_apigee-project_us-west1-a_apigee-cluster\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 `apigee-cluster` in the region `us-west1`, you would switch to the `gke_apigee-project_us-west1-a_apigee-cluster` context, as follows: \n\n ```\n kubectl config use-context gke_apigee-project_us-west1-a_apigee-cluster\n ```\n\n Where `gke_apigee-project_us-west1-a_apigee-cluster` is the name of the context to switch to.\n3. Check the current context to be sure it is set to the intended cluster. For example: \n\n ```\n kubectl config current-context\n gke_apigee-project_us-west1-a_apigee-cluster\n ```\n\nGrant cluster credentials\n-------------------------\n\n\n[Cluster credentials](https://cloud.google.com/sdk/gcloud/reference/container/clusters/get-credentials) give you access to the containers running in the cluster. Fetch your\ncredentials and grant yourself the **cluster-admin** role:\n\n1. Fetch the credentials: \n\n ```\n gcloud container clusters get-credentials cluster-name\n ```\n\n Where \u003cvar translate=\"no\"\u003ecluster-name\u003c/var\u003e is the name is the name of the cluster you created (the\n cluster into which you intend to install Apigee hybrid).\n2. Set the cluster role binding. Execute this command exactly as shown: \n\n ```\n kubectl create clusterrolebinding cluster-admin-binding \\\n --clusterrole cluster-admin --user $(gcloud config get-value account)\n ```\n\nSummary\n-------\n\n\nYou now have a Kubernetes cluster running in your GCP project. Your shell environment is\nset up, and you are ready to install the Apigee hybrid runtime plane software\non your local machine.\n[1](/apigee/docs/hybrid/v1.1/install-create-cluster) [(NEXT) Step 2: Install apigeectl](/apigee/docs/hybrid/v1.1/install-download-install) [3](/apigee/docs/hybrid/v1.1/install-copy-overrides) [4](/apigee/docs/hybrid/v1.1/install-apply-hybrid)\n\n\u003cbr /\u003e"]]
