다음 명령어를 사용하여 다운로드한 gzip 파일 콘텐츠를 방금 만든 기본 디렉터리에 추출합니다.
tar xvzf filename.tar.gz -C path-to-base-directory
cd 명령어를 사용하여 디렉터리를 기본 디렉터리로 변경합니다.
tar 콘텐츠는 기본적으로 이름에 해당 버전과 플랫폼이 포함된 디렉터리로 확장됩니다. 예를 들면 ./apigeectl_1.4.0-d591b23_linux_64입니다. 다음 명령어를 사용하여 디렉터리 이름을 apigeectl로 변경합니다.
mv apigeectl_1.4.0-d591b23_linux_64 apigeectl
다음 명령어를 사용하여 디렉터리로 변경합니다.
cd ./apigeectl
이 디렉터리는 apigeectl 홈 디렉터리입니다. 여기에 apigeectl 실행 가능한 명령어가 있습니다.
다음 명령어를 사용하여 이 홈 디렉터리 경로를 저장할 환경 변수를 만듭니다.
export APIGEECTL_HOME=$PWD
다음 명령어를 사용하여 변수에 올바른 경로가 포함되었는지 확인합니다.
echo $APIGEECTL_HOME
프로젝트 디렉터리 구조 설정
다음 디렉터리 구조는 권장되는 방식입니다. 이 방식은 Apigee Hybrid 출시 소프트웨어를 개발자가 만들어야 하는 구성 파일과 분리합니다. 만들려는 $APIGEECTL_HOME 변수 및 심볼릭 링크를 사용하면 원하는 경우 새 소프트웨어 버전으로 쉽게 전환할 수 있습니다. Apigee Hybrid 업그레이드도 참조하세요.
다음 명령어를 사용하여 기본 디렉터리(apigeectl 디렉터리가 있는 디렉터리)에 있는지 확인합니다.
cd $APIGEECTL_HOME/..
다음 명령어를 사용하여 hybrid-files라는 새 폴더를 만듭니다. 디렉터리에 원하는 이름을 지정할 수 있지만 문서에서는 hybrid-files 이름을 일관되게 사용합니다. 나중에 이 폴더에 구성 파일, 서비스 계정 키, TLS 인증서를 저장합니다. 이 폴더를 사용하면 구성 파일을 apigeectl 소프트웨어 설치와 별도로 유지할 수 있습니다.
[[["이해하기 쉬움","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 documentation refers to Apigee hybrid version 1.4, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eapigeectl\u003c/code\u003e is the command-line interface for installing and managing Apigee hybrid in a Kubernetes cluster, and steps are provided to download and install it.\u003c/p\u003e\n"],["\u003cp\u003eInstructions are provided to create a base directory, and extract the contents of the downloaded \u003ccode\u003eapigeectl\u003c/code\u003e archive.\u003c/p\u003e\n"],["\u003cp\u003eA suggested project directory structure is described to separate Apigee hybrid software from configuration files, and using symbolic links for easy version switching.\u003c/p\u003e\n"],["\u003cp\u003eThe setup includes creating specific subdirectories like \u003ccode\u003eoverrides\u003c/code\u003e, \u003ccode\u003eservice-accounts\u003c/code\u003e, and \u003ccode\u003ecerts\u003c/code\u003e inside the \u003ccode\u003ehybrid-files\u003c/code\u003e directory, along with symbolic links to \u003ccode\u003eapigeectl\u003c/code\u003e home directory.\u003c/p\u003e\n"]]],[],null,["# Step 4: Install apigeectl\n\n| You are currently viewing version 1.4 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\nThis step explains how to download and install [apigeectl](/apigee/docs/hybrid/v1.4/cli-reference),\nset up the installation directories, and create Google Cloud service accounts, and TLS credentials\nthat are required for Apigee hybrid to operate.\n\nDownload and install `apigeectl`\n--------------------------------\n\n`apigeectl` is the command-line interface\n(CLI) for installing and managing Apigee hybrid in a Kubernetes cluster.\n\nThe following steps describe how to get `apigeectl`:\n\n1. Store the latest version number in a variable using the following command: \n\n ```\n export VERSION=$(curl -s \\\n https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/current-version.txt?ignoreCache=1)\n ```\n | **Note:** Some MacOS terminal shells may return an error from this command. If you see an error, try running it without `?ignoreCache=1`, as follows: \n |\n | ```\n | export VERSION=$(curl -s \\\n | https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/current-version.txt)\n | ```\n2. Check that the variable was populated with a version number using the following command. If you want to use a different version, you can save that in an environment variable instead. \n\n ```\n echo $VERSION\n ``` \n\n ```\n 1.4.0\n ```\n3. Download the release package for your operating system using the following command:\n\n **Mac 64 bit:** \n\n ```\n curl -LO \\\n https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/$VERSION/apigeectl_mac_64.tar.gz\n ```\n\n **Linux 64 bit:** \n\n ```\n curl -LO \\\n https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/$VERSION/apigeectl_linux_64.tar.gz\n ```\n\n **Mac 32 bit:** \n\n ```\n curl -LO \\\n https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/$VERSION/apigeectl_mac_32.tar.gz\n ```\n\n **Linux 32 bit:** \n\n ```\n curl -LO \\\n https://storage.googleapis.com/apigee-release/hybrid/apigee-hybrid-setup/$VERSION/apigeectl_linux_32.tar.gz\n ```\n4. Create a directory on your system to serve as the **base directory** for the Apigee hybrid installation.\n5. Extract the downloaded gzip file contents into the base directory you just created using the\n following command:\n\n ```\n tar xvzf filename.tar.gz -C path-to-base-directory\n ```\n6. Change directory to the base directory using the `cd` command.\n7. The tar contents are, by default, expanded into a directory with the version and platform in\n its name. For example: `./apigeectl_1.4.0-d591b23_linux_64`. Rename that directory\n to `apigeectl` using the following command:\n\n ```\n mv apigeectl_1.4.0-d591b23_linux_64 apigeectl\n ```\n8. Change to the directory using the following command: \n\n cd ./apigeectl\n\n\n This directory is the `apigeectl` home directory. It is where the `apigeectl`\n executable command is located.\n9. Create an environment variable to hold this home directory path using the following command: \n\n ```\n export APIGEECTL_HOME=$PWD\n ```\n10. Verify that the variable holds the correct path using the following command: \n\n ```\n echo $APIGEECTL_HOME\n ```\n\nSet up the project directory structure\n--------------------------------------\n\n\nThe following directory structure is a suggested approach. It separates Apigee hybrid\nrelease software from configuration files that you must create. Through the use of the\n`$APIGEECTL_HOME` variable and symbolic links that you create, you can easily\nswitch to a new software version if you choose to. See also [Upgrading Apigee hybrid](/apigee/docs/hybrid/v1.4/upgrade).\n| **Note:** For the purpose of this quickstart, subsequent installation steps assume that you created the project structure as described in this section. If you follow this suggested structure, you can copy and paste most installation commands directly into your terminal.\n\n1. Be sure you are in the base directory (the directory where the `apigeectl` directory is located) by using the following command: \n\n ```\n cd $APIGEECTL_HOME/..\n ```\n2. Create a new folder called `hybrid-files` using the following command. You can give the directory any name you wish, but in the docs, the name `hybrid-files` is used consistently. Later, you will store configuration files, service account keys, and TLS certificates in this folder. This folder lets you keep your config files separate from the `apigeectl` software installation. \n\n ```\n mkdir hybrid-files\n ```\n3. The current directory structure now looks like the following: \n\n pwd && ls\n /hybrid-base-directory\n apigeectl\n hybrid-files\n\n4. Change directory into the `hybrid-files`folder using the following command: \n\n ```\n cd hybrid-files\n ```\n5. Inside the `hybrid-files` directory, create the following subdirectories to organize files that you will create later: \n\n mkdir overrides\n mkdir service-accounts\n mkdir certs\n\n6. Inside the `hybrid-files` directory, create the following symbolic links to `$APIGEECTL_HOME`. These links allow you to run the `apigeectl` command from inside the `hybrid-files` directory as the following example shows:\n | **Note:** If this is not the first time you have used this process, the following symbolic links\n | may already exist. Check to see if the links already exist using the\n | following command. If the directories exist, skip this step. \n |\n | ```\n | ls -l | grep ^l\n ``` \n\n ln -s `$APIGEECTL_HOME`/tools tools\n ln -s `$APIGEECTL_HOME`/config config\n ln -s `$APIGEECTL_HOME`/templates templates\n ln -s `$APIGEECTL_HOME`/plugins plugins\n\n7. To check that the symlinks were created correctly, execute the following command and make sure the link paths point to the correct locations: \n\n ```\n ls -l | grep ^l\n ```\n\n\nYou now have a home base from which you can configure, deploy, and manage Apigee hybrid\nin your Kubernetes cluster. Next, you will create the Google Cloud service accounts and credentials\nrequired to configure hybrid runtime components.\n[1](/apigee/docs/hybrid/v1.4/2-1-install-create-cluster) [2](/apigee/docs/hybrid/v1.4/2-2-install-cert-manager) [3](/apigee/docs/hybrid/v1.4/2-3-install-asm) [4](/apigee/docs/hybrid/v1.4/2-4-install-apigeectl) [(NEXT) Step 5: Set up service accounts](/apigee/docs/hybrid/v1.4/2-5-install-service-accounts) [6](/apigee/docs/hybrid/v1.4/2-6-install-configure-cluster) [7](/apigee/docs/hybrid/v1.4/2-7-install-hybrid-runtime)\n\n\u003cbr /\u003e"]]
