Immutable when deployed

• Asynchronous deployments
• Retrieving deployment status is based on the last time the runtime plane "checked-in" with the management plane

• Support for environment groups
• Self-service through the Apigee UI and APIs
• Flexibility in serving topology
• An MP pod can only serve one environment

For more information, seeAbout environments and environment groups.

Process unary gRPC-protocol API requests to a gRPC target server. SeeCreating gRPC API proxies.

Converts HTTP/1.1 header field names to lowercase when forwarded to the backend. This behavior may affect applications that expect case to be preserved.

• Northbound managed as Kubernetes secrets

• You can create encrypted, environment-scoped KVMs in the Apigee UI. KVMs are always encrypted. You cannot add, update, or view KVM entries in the UI.
• Use theprivate. attribute with all variables when accessing a KVM with theGET command to hide the KVM information in a debug (Trace) session. If theprivate. attribute is not used, the KVM is still encrypted; however, the KVM information will appear decrypted in the debug Trace) session and no exception will be thrown.
• You can manage KVM entries using thekeyvaluemaps.entries API or the KeyValueMapOperations policy.
• You can use property sets for some of the same use cases as KVMs. SeeUsing property sets.
• The<MapName> element enables the KeyValueMapOperations policy to identify which KVM to use dynamically, at runtime.

For more information on creating KVMs in the UI, seeUsing key value maps. See alsoAccessing configuration data for information on how to choose the right data persistence mechanism.

• Node.js API proxies are not supported.
• Apigee recommends that you host Node.js applications as separate containers in Kubernetes (same or different cluster)

• Managed through Google Cloud console's IAM service
• Some curated out-of-the-box roles are available
• You can create custom roles which can include other Google Cloud permissions

For more information, see Users and roles.

For hybrid:

• The ingress is implemented through Anthos Service Mesh.
• The keys and certs are deployed directly to Kubernetes.

For Apigee:

• Each instance exposes an HTTPS endpoint via self-signed certificate. The CA for the certificate can be downloaded by querying the org.

Defines only the length of the debug session. The starting point is when the Message Processor receives the request to run in debug mode.

Default value is 5 minutes if the session was initiated with the API and 10 minutes if it was initiated in the UI.

Data is persisted for 24 hours before hybrid automatically deletes it.

• created_by
• modified_by
• self