caapim/gateway repository overview

⁠Latest Tags

• Gateway 11.2.2: latest, 11.2.2, 11.2.2_20260831 (11.2.2 GA)

• Gateway 11.2.1: 11.2.1, 11.2.1_20260831 (11.2.1 GA + August 2026 MPP + MSP)

• Gateway 11.2.0: 11.2.0, 11.2.0_20260227 (11.2.0 GA + February 2026 MPP + MSP)

  • 11.2.0_20251128 (11.2.0 GA)

• Gateway 11.1.4: 11.1.4, 11.1.4_20260831 (11.1.4 GA + August 2026 MPP + MSP)

• Gateway 11.1.3: 11.1.3, 11.1.3_20260430 (11.1.3 GA + April 2026 MPP + MSP)

• Gateway 11.1.2: 11.1.2, 11.1.2_20250831 (11.1.2 + August 2025 MPP)

  • 11.1.2_20250328 (11.1.2 GA)

• Gateway 11.1.1: 11.1.1, 11.1.1_20250228 (11.1.1 + February 25 MPP)

  Note: The CR nomenclature is no longer used and will not be reintroduced for MPPs with minor releases from Gateway version 11.1 onward. The date-based tag for version 11.1 has been revised. The January 2025 MPP for 11.1 will be tagged as 11.1.1_20250131.

• Gateway 11.1: 11.1.00, 11.1.00_20240730 (11.1 GA + July 24 MPP)

  • 11.1.00_20240502 (11.1 GA)

• Gateway 11.0: 11.0.00_CR4, 11.0.00_20260130 (11.0 CR4 GA + January 2026 MPP)

  • Starting at 11.0 CR2, the base OS image is now using Red Hat Universal Base Image (ubi9-minimal) instead of CentOS. To learn more⁠

• Unsupported (experimental) tag: earlyaccess

  
  

Note: Tag 'earlyaccess' is a preview image for an upcoming release and is not supported. This tag is meant for evaluating new features and bug fixes. It should not be used for any production related workloads.

About Monthly Platform Patches

MPPs keep your Gateways updated and secure from recent OS-level vulnerabilities. New MPP-patched Gateway images apply to the latest version of the Gateway, including, if available, the latest CR. If you're on the base version or an early CR-version of the Gateway, you may need to upgrade to the latest CR to benefit from the current MPP.

Gateway Image Deployment Best Practices

Set up a private Docker image registry specifically for the Gateway images you plan to use in your production environments. This approach guarantees that your organization retains full control over the image's contents. This way, you won't expose your Gateways to any modifications pushed by Layer7 to the public caapim/gateway Docker registry. In situations where your organization wishes to use an image from the public caapim/gateway Docker registry to ensure up-to-date versions, it's strongly recommended to opt for the static 'Date-Stamped Version Tag' rather than relying on dynamic tags such as 'latest' or 'latest version'. This helps you prevent any unforeseen changes that could arise from dynamic tags and ensures a more controlled and consistent deployment process for your Gateways.

⁠What is the Layer7 API Gateway?

The Layer7 API Gateway is an XML firewall and service gateway that controls how web services are exposed to and accessed by external client applications. The Gateway provides runtime control over service-level authentication, authorization, key management, credentialing, integrity, confidentiality, schema validation, content inspection, data transformation, threat protection (including integration with external virus scanners for SOAP attachment scanning), routing, protocol switching, SLA enforcement, logging, and other functions.

Configured and managed through the GUI-based Policy Manager, the Gateway also acts as an integration point for extending existing PKI, Identity, SSO, federation and MOM infrastructures to web services, ensuring customers can leverage existing security and messaging infrastructure for web services and SOA initiatives.

⁠How to Use This Image

For instructions on how to use this image, see "Configuring the Container Gateway⁠"

⁠License

This is commercial software and requires the purchase of a commercial license before it may be used. Please contact Broadcom-Layer7 to obtain a license to use the Layer7 API Gateway beyond evaluation purposes. New Gateway licenses can be requested through the Customer Care Web Form⁠. When filling out the form, be sure to select Licensing - CA Enterprise Software as the Request Type.

You must have a valid commercial license to Layer7 API Gateway and accept the terms of the End User License Agreement (“CA EULA”) before using Layer7 API Gateway. By setting the ACCEPT_LICENSE environment variable to “true,” you are expressing that you have a valid and existing commercial license for CA API Gateway and that you have reviewed and accepted the terms of the CA EULA⁠, which shall govern your use of CA API Gateway.

To learn more about the API Full Lifecycle Management product suite from Broadcom, please see https://www.broadcom.com/products/software/api-management⁠

⁠Supported Docker Versions

See Container Gateway Platform Support⁠ for details regarding which platforms and corresponding versions are supported by the Container Gateway.

Please see the Docker installation documentation⁠ for details on how to upgrade your Docker daemon and OpenShift Origin installation documentation⁠ for details on how to upgrade your OpenShift server.

⁠User Feedback

If you have any problems with or questions about this image, please contact Broadcom Support at:

https://www.broadcom.com/support/software/contact⁠

⁠User Documentation

Visit Broadcom-Layer7 Tech Docs⁠ to view the online documentation for the CA API Gateway.