This step explains how to create the TLS credentials
that are required for Apigee hybrid to operate.
Create TLS certificates
You are required to provide TLS certificates for the runtime ingress gateway in your
Apigee hybrid configuration. For the purpose of this quickstart (a non-production trial installation),
the runtime gateway can accept self-signed credentials. In the following steps,
openssl is used to generate the self-signed credentials.
In this step, you will create the TLS credential files and add them to
the $HYBRID_FILES/certs directory.
In Step 6: Configure the
hybrid runtime, you will add the file paths to the cluster configuration file.
Execute the following command to create the credential files and store them in your
$HYBRID_FILES/certs directory:
DOMAIN is the domain you provided as the hostname for the environment
group you created in Create an environment group.
ENV_GROUP_NAME 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.
This command creates a self-signed certificate/key pair that you can use for the quickstart
installation.
If you have additional environment groups with unique domain names, just repeat this step
for each one. You will reference these groups and certificates in the cluster configuration
step.
Check to make sure the files are in the $HYBRID_FILES/certs directory using the following command:
Where keystore_ENV_GROUP_NAME.pem is the self-signed TLS certificate file and keystore_ENV_GROUP_NAME.key
is the key file.
You now have the credentials needed to manage Apigee hybrid
in your Kubernetes cluster. Next, you will create a file that is used by Kubernetes
to deploy the hybrid runtime components to the cluster.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-10 UTC."],[[["This document provides instructions for creating TLS credentials required for the Apigee hybrid runtime ingress gateway, and notes that version 1.8 of the documentation is at end of life."],["For non-production trial installations, self-signed credentials can be generated using `openssl` as outlined in the steps."],["In production environments, signed certificates are required, either via a certificate/key pair or a Kubernetes secret, with a linked example of how to use *Lets Encrypt* as a CA."],["The generated TLS credential files should be placed in the `$HYBRID_FILES/certs` directory, which will then be referenced in the cluster configuration file in step 6."],["The steps include creating self signed certs for each group, as well as where they should be stored, with instructions on how to verify they are in the right place."]]],[]]
