[[["わかりやすい","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-08-18 UTC。"],[[["\u003cp\u003eThis documentation explains the process of creating TLS credentials required for Apigee hybrid, specifically for the runtime ingress gateway.\u003c/p\u003e\n"],["\u003cp\u003eFor a non-production, quickstart setup, self-signed TLS certificates generated using openssl are acceptable, whereas production environments require signed certificates.\u003c/p\u003e\n"],["\u003cp\u003eThe necessary TLS credential files, including a \u003ccode\u003e.pem\u003c/code\u003e or \u003ccode\u003e.crt\u003c/code\u003e certificate file and a \u003ccode\u003e.key\u003c/code\u003e key file, are created and stored within the \u003ccode\u003e$APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs\u003c/code\u003e directory.\u003c/p\u003e\n"],["\u003cp\u003eThe provided command generates a self-signed certificate/key pair, which is then used for the quickstart installation and should be repeated for any additional environment groups, ensuring unique domain names and corresponding certificates.\u003c/p\u003e\n"],["\u003cp\u003eAfter generating the TLS certificates, you will need to reference them in the cluster configuration file, which will be done in Step 6, and you can confirm their existence using the command \u003ccode\u003els $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
