From OpenAPI to gateway: Building your first APIOps pipeline
APIOps is about applying Infrastructure-as-Code (IaC) and GitOps to the management of APIs. Teams that want increased levels of automation, reliability, and scalability in the way they manage APIs are investing in APIOps.
For an APIOps initiative to succeed, you need to be clear about what kind of developer experience you want to provide to your API publishers. Generally speaking, your objectives are twofold:
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
From OpenAPI to gateway: Building your first APIOps pipeline
APIOps is about applying Infrastructure-as-Code (IaC) and GitOps to the management of APIs. Teams that want increased levels of automation, reliability, and scalability in the way they manage APIs are investing in APIOps.
Presented by
Panelist
Panelist
Panelist
Moderator
.avif)
Brent Hunter
Senior Solutions Engineer, Gravitee
For an APIOps initiative to succeed, you need to be clear about what kind of developer experience you want to provide to your API publishers. Generally speaking, your objectives are twofold:
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
From OpenAPI to gateway: Building your first APIOps pipeline
APIOps is about applying Infrastructure-as-Code (IaC) and GitOps to the management of APIs. Teams that want increased levels of automation, reliability, and scalability in the way they manage APIs are investing in APIOps.
Presented by
For an APIOps initiative to succeed, you need to be clear about what kind of developer experience you want to provide to your API publishers. Generally speaking, your objectives are twofold:
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
1. For API publishers to have autonomy in creating and managing APIs, sometimes even abstracting away some of the details of the underlying API management platform.
2. Automatically enforce guardrails and corporate policies, so that all APIs meet your organization's security requirements.
The starting point for API Publishers in an APIOps platform is typically an API configuration file. Depending on how you operate, this could be an OpenAPI definition, AsyncAPI definition, a Kubernetes resource file, a vendors’ API definition, you name it. These API configuration files are the source of truth for how your APIs should be configured in your API Management & Gateway platform.
In this workshop, Brent Hunter, Senior Solutions Engineer at Gravitee, will take you through an example of how to create an APIOps platform that starts from an OpenAPI definition, and uses a GitHub repository, a GitHub Action, ArgoCD, and the Gravitee Kubernetes Operator.
From OpenAPI to gateway: Building your first APIOps pipeline
APIOps is about applying Infrastructure-as-Code (IaC) and GitOps to the management of APIs. Teams that want increased levels of automation, reliability, and scalability in the way they manage APIs are investing in APIOps.
Presented by
Panelist
Panelist
Panelist
Host
Brent Hunter
Senior Solutions Engineer, Gravitee
Tell everyone
Sign up now
