Skip to content

Proxy to External Services

As an application grows, sites typically start to integrate with external services. These external services can range from APIs for offloading resource intensive tasks to completely separate sites which are built for a sub section of the site eg. https://example.com/site2.

Skpr provides development teams with the ability to connect their application to others via the edge layer.

Overview

Usage

The example configuration below routes all /api requests to the api.example.com origin.

Requests to the origin will have the SECRET cookie and HOST header forwarded.

ingress:
  proxy:
    api:
      path: /api*
      origin: api.example.com
      forward:
        cookies:
          - SECRET
        headers:
          - HOST

Benefits

  • External services can will be cached by the Skpr edge layer.
  • Development teams will have a high level view of the applications health eg. How many 5xx responses occured for the application and its external services.
  • External application will inherit Skprs certificate management and WAF rules.

Roadmap

In a future release environments will be able to have proxy routing rules which can reference other project environments running on the same cluster.

This API is an early draft and may change during the development process.

ingress:
  proxy:
    api:
      path: /api
      origin: project2/dev
      type: environment