Apigee Hybrid on OCI (OKE)

Google Cloud Apigee
, ,
1

i everyone,

I’m evaluating a hybrid API management architecture using Apigee Hybrid and would like to clarify a point regarding platform support vs Kubernetes compatibility.

From the official documentation, I understand that Apigee Hybrid is certified for specific platforms (GKE, EKS, AKS, etc.), but fundamentally relies on Kubernetes (with supported versions and Istio).

In this context, I’m considering running the runtime plane on Oracle Kubernetes Engine (OKE), which provides a CNCF-conformant “vanilla” Kubernetes environment.

Given that:

  • OKE is standard Kubernetes (no major vendor-specific abstractions)
  • It supports compatible Kubernetes versions and typical ingress/Istio setups
  • Apigee Hybrid is designed to run on Kubernetes clusters

My questions are:

  1. Has anyone successfully deployed Apigee Hybrid on OKE (OCI)?
  2. Are there any known limitations or blockers compared to officially supported platforms?
  3. From a support perspective, would this be considered a “best-effort” scenario?
  4. Any recommendations around networking (especially control plane connectivity to GCP) or ingress setup in this type of environment?

Appreciate any real-world experiences or guidance.

Thanks!

2

Welcome to the Apigee community @acer :slightly_smiling_face: we’ll continue to monitor this thread and invite other members to share their insights. In the meantime, please review the resources below, which I hope will be helpful to your question:

I’d also love to invite you to our Community Tech Talk this week on April 16 at 5 PM CEST. It’s a fantastic opportunity to connect with Googler and community experts live:

Powering Retail Agents with ADK, UCP & Apigee X | :tickets: Register here!

Hope to see you there!

3

Answering your questions in the same order:

  1. I have a reasonable perspective of active Apigee hybrid deployments in the wild and am not aware of any deployments on OKE.
  2. No, not really. As far as what the Apigee hybrid runtime is and requires, it’s all pretty standard stuff. The need to install CRDs, an operator, and the requirement for PersistentVolume resources is about as advanced the requirements get.
  3. Yes, you could call it “best-effort”, however, Google Support reserves the right to fallback to a zero or minimum level of best-effort support if the product is not being operated within the official parameters clearly instructed and stated in documentation.
  4. I don’t have any gotchas or quirks to share. All communication with the Apigee control plane occurs over apigee.googleapis.com and apigeeconnect.googleapis.com (used only by Apigee Connect). You can optionally establish a private network connection (e.g. using Cloud VPN, or Cloud Interconnect) to Google Cloud and use Private Google Access (PGA) to access the same services via private.googleapis.com as per https://docs.cloud.google.com/vpc/docs/configure-private-google-access. Note that you can take this further, with VPC Service Controls, using restricted.googleapis.com (as mentioned on the same page). Ingress setup is more straightforward. The product ships with an Ingress Gateway, powered by Envoy. You can configure this in different ways using the ingressGateways, istiod and virtualhosts stanzas in your overrides.yaml file. After installation, you will have ingress gateways and a corresponding Kubernetes Service. How you choose to expose it further is entirely your choice, as per https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/install-expose-apigee-ingress

In future, when speaking with Google regarding OKE support for Apigee hybrid, feel free to share b/332890152 with the Googler.

I hope this helps.