Langkah ini menjelaskan cara membuat kredensial TLS
yang diperlukan agar Apigee hybrid dapat beroperasi.
Membuat sertifikat TLS
Anda harus memberikan sertifikat TLS untuk gateway ingress runtime dalam konfigurasi hibrida Apigee. Untuk tujuan panduan memulai ini (penginstalan uji coba non-produksi), gateway runtime dapat menerima kredensial yang ditandatangani sendiri. Pada langkah-langkah berikut,
openssl digunakan untuk membuat kredensial yang ditandatangani sendiri.
Pada langkah ini, Anda akan membuat file kredensial TLS dan menambahkannya ke direktori $APIGEE_HELM_CHARTS_HOME/certs.
Di
Langkah 6: Membuat penggantian, Anda akan menambahkan jalur file ke file konfigurasi
cluster.
Buat direktori untuk file kredensial. Diagram Helm tidak dapat membaca file di luar direktori diagram, dan kredensial TLS dikelola dengan diagram apigee-virtualhost.
Oleh karena itu, buat direktori untuk file kredensial dalam
direktori $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/.
DOMAIN adalah domain yang Anda berikan sebagai nama host untuk grup lingkungan yang Anda buat di Membuat grup lingkungan.
ENV_GROUP adalah nama grup lingkungan tempat domain ditentukan sebagai nama host. Sebaiknya sertakan nama grup lingkungan dalam nama kunci dan keystore untuk menghindari penggunaan kembali nilai domain yang sama secara tidak sengaja jika Anda membuat kunci untuk beberapa grup lingkungan.
Perintah ini membuat pasangan kunci/sertifikat yang ditandatangani sendiri yang dapat Anda gunakan untuk penginstalan
quickstart.
Jika Anda memiliki grup lingkungan tambahan dengan nama domain unik, ulangi langkah ini untuk setiap grup lingkungan. Anda akan mereferensikan grup dan sertifikat ini di langkah konfigurasi
cluster.
Periksa untuk memastikan file berada di direktori $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs menggunakan perintah berikut:
ls $APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs
Anda akan melihat dua file:
keystore_ENV_GROUP.pem atau keystore_ENV_GROUP.crt adalah file sertifikat TLS yang ditandatangani sendiri.
keystore_ENV_GROUP.key
adalah file kunci.
Sekarang Anda memiliki kredensial yang diperlukan untuk mengelola Apigee hybrid di cluster Kubernetes. Selanjutnya, Anda akan membuat file penggantian yang digunakan oleh Kubernetes untuk men-deploy komponen runtime campuran ke cluster.
[[["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\u003eTLS certificates are necessary for the Apigee hybrid runtime ingress gateway, and for a quickstart, self-signed credentials generated with openssl are acceptable.\u003c/p\u003e\n"],["\u003cp\u003eCredential files should be created within the \u003ccode\u003e$APIGEE_HELM_CHARTS_HOME/apigee-virtualhost/certs\u003c/code\u003e directory, as they are managed by the \u003ccode\u003eapigee-virtualhost\u003c/code\u003e chart, and Helm charts cannot read files outside the chart directory.\u003c/p\u003e\n"],["\u003cp\u003eUse the provided openssl command to generate the self-signed certificate and key pair, replacing \u003ccode\u003eDOMAIN\u003c/code\u003e and \u003ccode\u003eENV_GROUP\u003c/code\u003e with your specific values, and if you are using multiple groups, repeat the command for each domain.\u003c/p\u003e\n"],["\u003cp\u003eAfter generating, confirm the \u003ccode\u003ekeystore_<ENV_GROUP>.pem\u003c/code\u003e (or \u003ccode\u003e.crt\u003c/code\u003e) and \u003ccode\u003ekeystore_<ENV_GROUP>.key\u003c/code\u003e files exist in the designated directory.\u003c/p\u003e\n"],["\u003cp\u003eIn a production setting, you need to use signed certificates instead of self-signed certificates.\u003c/p\u003e\n"]]],[],null,["# Step 5: Create TLS certificates\n\n| You are currently viewing version 1.14 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.14/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.14/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.14/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.14/install-create-cluster) [2](/apigee/docs/hybrid/v1.14/install-download-charts) [3](/apigee/docs/hybrid/v1.14/install-create-namespace) [4](/apigee/docs/hybrid/v1.14/install-service-accounts) [5](/apigee/docs/hybrid/v1.14/install-create-tls-certificates) [(NEXT) Step 6: Create the overrides](/apigee/docs/hybrid/v1.14/install-create-overrides) [7](/apigee/docs/hybrid/v1.14/install-enable-control-plane-access) [8](/apigee/docs/hybrid/v1.14/install-cert-manager) [9](/apigee/docs/hybrid/v1.14/install-crds) [10](/apigee/docs/hybrid/v1.14/install-helm-charts) [11](/apigee/docs/hybrid/v1.14/install-workload-identity)\n\n\u003cbr /\u003e"]]