이 단계에서는 Apigee Hybrid 작동에 필요한 TLS 사용자 인증 정보를 만드는 방법을 설명합니다.
TLS 인증서 만들기
Apigee Hybrid 구성에 런타임 인그레스 게이트웨이에 대한 TLS 인증서를 제공해야 합니다. 이 빠른 시작(비프로덕션 무료 체험판 설치)에서 런타임 게이트웨이는 자체 서명 사용자 인증 정보를 수락할 수 있습니다. 다음의 절차에서 openssl은 자체 서명 사용자 인증 정보를 생성하는 데 사용됩니다.
이 단계에서는 TLS 사용자 인증 정보 파일을 만들어 $APIGEE_HELM_CHARTS_HOME/certs 디렉터리에 추가합니다.
6단계: 재정의 만들기에서는 파일 경로를 클러스터 구성 파일에 추가합니다.
사용자 인증 정보 파일을 위한 디렉터리를 만듭니다. Helm 차트는 차트 디렉터리 외부의 파일을 읽을 수 없으며 TLS 사용자 인증 정보는 apigee-virtualhost 차트로 관리됩니다.
따라서 $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/ 디렉터리 내에 사용자 인증 정보 파일을 위한 디렉터리를 만듭니다.
[[["이해하기 쉬움","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\u003eTLS credentials are required for the Apigee hybrid runtime ingress gateway, and for a quickstart installation, self-signed credentials generated with \u003ccode\u003eopenssl\u003c/code\u003e can be used.\u003c/p\u003e\n"],["\u003cp\u003eCreate a directory within \u003ccode\u003e$APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/\u003c/code\u003e to store the credential files, as Helm charts can only read files within the chart directory.\u003c/p\u003e\n"],["\u003cp\u003eRun the provided \u003ccode\u003eopenssl\u003c/code\u003e command to generate the self-signed certificate and key pair, naming them \u003ccode\u003ekeystore_$ENV_GROUP.pem\u003c/code\u003e and \u003ccode\u003ekeystore_$ENV_GROUP.key\u003c/code\u003e, respectively, where \u003ccode\u003e$ENV_GROUP\u003c/code\u003e is the name of your environment group.\u003c/p\u003e\n"],["\u003cp\u003eIf using additional environment groups, repeat the credential creation step for each, ensuring unique domain names are used.\u003c/p\u003e\n"],["\u003cp\u003eVerify the creation of the \u003ccode\u003ekeystore_\u003c/code\u003e\u003cvar translate=no\u003eENV_GROUP\u003c/var\u003e\u003ccode\u003e.pem\u003c/code\u003e or \u003ccode\u003ekeystore_\u003c/code\u003e\u003cvar translate=no\u003eENV_GROUP\u003c/var\u003e\u003ccode\u003e.crt\u003c/code\u003e and \u003ccode\u003ekeystore_\u003c/code\u003e\u003cvar translate=no\u003eENV_GROUP\u003c/var\u003e\u003ccode\u003e.key\u003c/code\u003e files within the \u003ccode\u003ecerts\u003c/code\u003e directory.\u003c/p\u003e\n"]]],[],null,["# Step 5: Create TLS certificates\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis step explains how to create the TLS credentials\nthat are required for Apigee hybrid to operate.\n\nCreate TLS certificates\n-----------------------\n\n\nYou are required to provide TLS certificates for the runtime ingress gateway in your\nApigee hybrid configuration. For the purpose of this quickstart (a non-production trial installation),\nthe runtime gateway can accept self-signed credentials. In the following steps,\n[openssl](https://www.openssl.org/) is used to generate the self-signed credentials.\n| **Note:** In a production environment, you will need to use signed certificates. You can use either a certificate and key pair or a Kubernetes secret. For an example on how to obtain a TLS certificate from the *Lets Encrypt* certificate authority (CA), see [Obtain TLS credentials: An example](/apigee/docs/hybrid/v1.13/lets-encrypt).\n\n\nIn this step, you will create the TLS credential files and add them to\nthe `$APIGEE_HELM_CHARTS_HOME/certs` directory.\nIn [Step 6: Create the overrides](/apigee/docs/hybrid/v1.13/install-configure-cluster), you will add the file paths to the cluster\nconfiguration file.\n\n1. Create a directory for the credential files. Helm charts cannot read files outside the chart directory, and the TLS credentials are managed with the `apigee-virtualhost` chart. therefore create your directory for the credential files within the \u003cvar translate=\"no\"\u003e$APIGEE_HELM_CHARTS_HOME\u003c/var\u003e`/apigee-virtualhost/` directory.\n\n For example: \n\n ```\n mkdir $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs/\n ```\n2. Execute the following command to create the credential files and store them in your `$APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs` directory: \n\n ```\n openssl req -nodes -new -x509 -keyout $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs/keystore_$ENV_GROUP.key -out \\\n $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs/keystore_$ENV_GROUP.pem -subj '/CN='\u003cvar translate=\"no\"\u003e$DOMAIN\u003c/var\u003e'' -days 3650\n ```\n\n\n Where:\n - \u003cvar translate=\"no\"\u003eDOMAIN\u003c/var\u003e is the domain you provided as the hostname for the environment group you created in [Create an environment group](/apigee/docs/hybrid/v1.13/precog-add-environment#create-an-environment-group).\n - \u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e is the name of the environment group where the domain is specified as a hostname. It's a good practice to include the environment group name in the key and keystore name to avoid accidentally reusing the same domain value if you create keys for multiple environment groups.\n\n\n This command creates a self-signed certificate/key pair that you can use for the quickstart\n installation.\n\n\n If you have additional environment groups with unique domain names, repeat this step for each\n environment group. You will reference these groups and certificates in the cluster\n configuration step.\n3. Check to make sure the files are in the `$APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs` directory using the following command: \n\n ```\n ls $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs\n ```\n\n This you should see two files:\n - `keystore_`\u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e`.pem` or `keystore_`\u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e`.crt` is the self-signed TLS certificate file.\n - `keystore_`\u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e`.key` is the key file.\n\n\nYou now have the credentials needed to manage Apigee hybrid\nin your Kubernetes cluster. Next, you will create an overrides file that is used by Kubernetes\nto deploy the hybrid runtime components to the cluster.\n\nNext step\n---------\n\n\u003cbr /\u003e\n\n[1](/apigee/docs/hybrid/v1.13/install-create-cluster) [2](/apigee/docs/hybrid/v1.13/install-download-charts) [3](/apigee/docs/hybrid/v1.13/install-create-namespace) [4](/apigee/docs/hybrid/v1.13/install-service-accounts) [5](/apigee/docs/hybrid/v1.13/install-create-tls-certificates) [(NEXT) Step 6: Create the overrides](/apigee/docs/hybrid/v1.13/install-create-overrides) [7](/apigee/docs/hybrid/v1.13/install-enable-synchronizer-access) [8](/apigee/docs/hybrid/v1.13/install-cert-manager) [9](/apigee/docs/hybrid/v1.13/install-crds) [10](/apigee/docs/hybrid/v1.13/install-helm-charts) [11](/apigee/docs/hybrid/v1.13/install-workload-identity)\n\n\u003cbr /\u003e"]]
