Langkah ini menjelaskan cara menyiapkan lingkungan shell dan membuat cluster GKE di project Google Cloud Platform (GCP).
Menyiapkan shell terminal
Alat gcloud menyediakan antarmuka command line utama untuk GCP, dan kubectl menyediakan antarmuka command line utama untuk menjalankan perintah terhadap cluster Kubernetes.
Pastikan Anda telah menginstal gcloud dan kubectl di
shell lokal. Alat gcloud menyediakan antarmuka command line utama untuk GCP, dan kubectl menyediakan antarmuka command line utama untuk menjalankan perintah terhadap cluster Kubernetes.
gcloud -hkubectl -h
Jika Anda belum menginstal utilitas ini, instal sekarang:
Setelah menginstal Cloud SDK, instal alat command line kubectl dengan
menjalankan perintah berikut:
gcloud components install kubectl
Gunakan alat gcloud untuk mengonfigurasi dua setelan default: project dan region komputasi default Anda.
Mengonfigurasi setelan ini akan mempermudah Anda menjalankan perintah gcloud,
karena gcloud mengharuskan Anda menentukan project dan zona komputasi tempat
Anda ingin bekerja.
Untuk mencantumkan setelan saat ini:
gcloud config list
Jika project dan/atau zona komputasi tidak tercantum, Anda harus menambahkannya dengan perintah yang ditampilkan di bawah. Jika, dari output daftar, Anda memutuskan bahwa Anda perlu mengalihkan setelan saat ini
untuk mencerminkan project dan region komputasi (atau zona), Anda juga dapat menggunakan perintah ini:
gcloud config set project project-idgcloud config set compute/region compute-regiongcloud config set compute/zone compute-zone
Dengan project-id sebagai nama project GCP Anda, compute-region adalah
nama region komputasi GCP, dan compute-zone adalah
nama zona komputasi GCP. Misalnya: compute/region us-central1. Untuk mengetahui daftar
region dan zona komputasi, lihat
Region dan zona yang tersedia.
Membuat cluster GKE
Pada langkah ini, Anda akan membuat cluster Kubernetes di project GCP (project yang Anda tetapkan dengan perintah gcloud config).
Jalankan perintah berikut untuk membuat cluster. Jenis mesin, jumlah node, dan
setelan lainnya yang ditentukan dalam perintah akan membuat cluster yang dikonfigurasi secara minimal dan cocok untuk
penginstalan Apigee Hybrid uji coba.
Dengan cluster-name adalah nama yang Anda pilih untuk cluster.
Pembuatan cluster dapat memerlukan waktu beberapa menit. Setelah berhasil, Anda akan melihat output yang mirip dengan
berikut dengan status RUNNING:
NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
apigee-hybrid us-central1-a 1.14.10-gke.27 35.222.54.89 n1-standard-4 1.14.10-gke.27 RUNNING
Menetapkan konteks saat ini
Konteks adalah grup parameter akses. Setiap konteks berisi cluster Kubernetes,
pengguna, dan namespace. Konteks saat ini adalah cluster yang saat ini menjadi default untuk
kubectl: semua perintah kubectl dijalankan pada cluster tersebut.
Pastikan konteks gcloud saat ini ditetapkan ke cluster yang baru saja Anda buat.
Pertama, cantumkan konteks untuk menentukan konteks saat ini. Dalam
contoh berikut, konteks saat ini adalah gke_hybrid-project_us-central1-a_apigee-hybrid.
Nama tersebut mencakup nama project GCP (hybrid-project), region atau zona
(us-central1-a), dan nama cluster (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
Jika perlu, tetapkan konteks saat ini ke cluster yang baru saja Anda buat (cluster
tempat Anda ingin menginstal Apigee hybrid). Dengan asumsi output get-contexts sebelumnya,
jika nama cluster yang Anda buat adalah apigee-cluster di region us-west1, Anda akan beralih ke
konteks gke_apigee-project_us-west1-a_apigee-cluster, sebagai berikut:
Kredensial cluster memberi Anda akses ke penampung yang berjalan di cluster. Ambil kredensial Anda dan berikan peran cluster-admin kepada diri Anda sendiri:
Sekarang Anda memiliki cluster Kubernetes yang berjalan di project GCP. Lingkungan shell Anda telah
disiapkan, dan Anda siap menginstal software platform runtime hibrida Apigee
di komputer lokal.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[[["\u003cp\u003eThis documentation pertains to Apigee hybrid version 1.2, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eBefore proceeding, users must ensure they have \u003ccode\u003egcloud\u003c/code\u003e and \u003ccode\u003ekubectl\u003c/code\u003e installed, and if not, they need to install them using the provided instructions.\u003c/p\u003e\n"],["\u003cp\u003eUsers should configure their default GCP project and compute region/zone using the \u003ccode\u003egcloud\u003c/code\u003e tool to streamline command execution.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves creating a GKE cluster using a \u003ccode\u003egcloud\u003c/code\u003e command, ensuring the default Kubernetes version meets requirements, and setting the current context to the newly created cluster using \u003ccode\u003ekubectl\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eUsers must fetch cluster credentials using \u003ccode\u003egcloud\u003c/code\u003e and grant themselves the \u003ccode\u003ecluster-admin\u003c/code\u003e role with a \u003ccode\u003ekubectl\u003c/code\u003e command for access to containers in the cluster.\u003c/p\u003e\n"]]],[],null,["# Step 1: Create a GKE cluster\n\n| You are currently viewing version 1.2 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 from v1.1.x to v1.2.0, see [Upgrading Apigee hybrid](/apigee/docs/hybrid/v1.2/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 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/docs/concepts/sandbox-pods) 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| We recommend you check the default Kubernetes version and make sure it meets the version\n| requirements listed in [Supported platforms](/apigee/docs/hybrid/v1.2/install-before-begin#supported-platforms).\n| To determine which Kubernetes version is the default, use this command: \n|\n| ```\n| gcloud container get-server-config\n| ```\n|\n|\n| If you don't want to use the default, you can add the `--cluster-version` flag to the cluster\ncreation command. For details, see [gcloud container clusters create.](https://cloud.google.com/sdk/gcloud/reference/container/clusters/create) \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.14.10-gke.27 35.222.54.89 n1-standard-4 1.14.10-gke.27 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.2/install-create-cluster) [(NEXT) Step 2: Install apigeectl](/apigee/docs/hybrid/v1.2/install-download-install) [3](/apigee/docs/hybrid/v1.2/install-copy-overrides) [4](/apigee/docs/hybrid/v1.2/install-apply-hybrid)\n\n\u003cbr /\u003e"]]
