Integrating Swagger API specifications into the API gateway configuration workflow with GitOps
Presented by Anees Anakkot (Citrix)
Q&A session Thu Nov 12, 6:30am Pacific time. Register: https://bit.ly/converge2020reg
This session demonstrates how API Gateway configuration workflows can leverage Swagger specifications for policy configuration to simplify the deployment and bring API developers closer to Operations.
Developers typically publish RESTful API specifications in the form of Swagger, compliant with the Open API standard. Swagger specifications contain policy-related information such as authentication and authorization, alongside detailed information about the APIs.
In this session, GitOps is used to deliver Swagger specifications to the API Gateway control plane in a Kubernetes environment. As developers are already using git as part of their workflow, leveraging the same into the Ops workflow is the next logical step to bridge both worlds.
The Solution consists of the following:
API Gateway CRD for linking Swagger API resource definitions with Policy templates
Supports Rate limiting, WAF, Authentication, Rewrite, Content routing API Gateway configurations
Supports all major GIT vendors