Este passo explica como criar as credenciais TLS necessárias para o funcionamento do Apigee hybrid.
Crie certificados TLS
Tem de fornecer certificados TLS para o gateway de entrada de tempo de execução na sua configuração híbrida do Apigee. Para efeitos deste início rápido (uma instalação de avaliação não de produção),
o gateway de tempo de execução pode aceitar credenciais autoassinadas. Nos passos seguintes, é usado o openssl para gerar as credenciais autoassinadas.
Neste passo, vai criar os ficheiros de credenciais TLS e adicioná-los ao diretório base_directory/hybrid-files/certs.
No Passo 7: configure o
tempo de execução híbrido, vai adicionar os caminhos dos ficheiros ao ficheiro de configuração do cluster.
Este comando cria um par de chaves/certificado autoassinado que pode usar para a instalação de início rápido.
Verifique se os ficheiros estão no diretório ./certs através do seguinte comando:
ls ./certs
keystore.pem
keystore.key
Em que keystore.pem é o ficheiro de certificado TLS autoassinado e keystore.key
é o ficheiro de chave.
Agora, tem as credenciais necessárias para gerir o Apigee hybrid no seu cluster do Kubernetes. Em seguida, vai criar um ficheiro usado pelo Kubernetes
para implementar os componentes do tempo de execução híbrido no cluster.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eThis documentation version (1.5) is end-of-life, and upgrading to a newer version is recommended.\u003c/p\u003e\n"],["\u003cp\u003eTLS certificates are required for the Apigee hybrid runtime ingress gateway, and this step provides the instructions to create them.\u003c/p\u003e\n"],["\u003cp\u003eFor a non-production trial, self-signed credentials can be generated using openssl; however, production environments necessitate signed certificates.\u003c/p\u003e\n"],["\u003cp\u003eThe provided openssl command creates a self-signed certificate/key pair (keystore.pem and keystore.key) within the \u003ccode\u003ehybrid-files/certs\u003c/code\u003e directory, which will be used in later steps.\u003c/p\u003e\n"]]],[],null,["# Step 6: Create TLS certificates\n\n| You are currently viewing version 1.5 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 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 either 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.5/lets-encrypt).\n\n\nIn this step, you will create the TLS credential files and add them to\nthe \u003cvar translate=\"no\"\u003ebase_directory\u003c/var\u003e`/hybrid-files/certs` directory.\nIn [Step 7: Configure the\nhybrid runtime](/apigee/docs/hybrid/v1.5/install-configure-cluster), you will add the file paths to the cluster configuration file.\n\n1. Be sure that you are in the \u003cvar translate=\"no\"\u003ebase_directory\u003c/var\u003e`/hybrid-files` directory you configured in [Set up the project directory structure](#setup-directory).\n2. Make sure to save a domain name to the **`DOMAIN`** environment variable using the following command: \n\n ```\n echo $DOMAIN\n ```\n3. Execute the following command from inside the `hybrid-files` directory: \n\n ```\n openssl req -nodes -new -x509 -keyout ./certs/keystore.key -out \\\n ./certs/keystore.pem -subj '/CN='$DOMAIN'' -days 3650\n ```\n\n\n Where **`DOMAIN`** is the same one you used for your environment in\n [Part 1, Step 5: Create an\n environment group](/apigee/docs/hybrid/v1.5/precog-add-environment).\n\n\n This command creates a self-signed certificate/key pair that you can use for the quickstart\n installation.\n4. Check to make sure the files are in the `./certs` directory using the following command: \n\n ls ./certs\n keystore.pem\n keystore.key\n\n\n Where `keystore.pem` is the self-signed TLS certificate file and `keystore.key`\n is the key file.\n\n\nYou now have the credentials needed to manage Apigee hybrid\nin your Kubernetes cluster. Next, you will create a file that is used by Kubernetes\nto deploy the hybrid runtime components to the cluster.\n[1](/apigee/docs/hybrid/v1.5/install-create-cluster) [2](/apigee/docs/hybrid/v1.5/install-cert-manager) [3](/apigee/docs/hybrid/v1.5/install-asm) [4](/apigee/docs/hybrid/v1.5/install-apigeectl) [5](/apigee/docs/hybrid/v1.5/install-service-accounts) [6](/apigee/docs/hybrid/v1.5/install-create-tls-certificates) [(NEXT) Step 7: Configure the hybrid runtime](/apigee/docs/hybrid/v1.5/install-configure-cluster) [8](/apigee/docs/hybrid/v1.5/install-enable-synchronizer-access) [9](/apigee/docs/hybrid/v1.5/install-hybrid-runtime)\n\n\u003cbr /\u003e"]]
