If you're interested in learning more about API Exposure in Kyma, follow these links to:

• Perform some simple and more advanced tasks:

  • Create a workload
  • Set up a custom domain for a workload
  • Expose a workload
  • Expose multiple workloads on the same host
  • Expose and secure a workload with OAuth2
  • Get a JWT
  • Expose and secure a workload with Istio
  • Expose and secure a workload with JWT

• Troubleshoot API Exposure-related issues when:

  • You cannot connect to a service exposed by an APIRule
  • You get the 401 Unauthorized or 403 Forbidden status code when you try to connect to a service exposed by an APIRule
  • You get the 404 Not Found status code when you try to connect to a service exposed by an APIRule
  • You get the 500 Internal Server Error status code when you try to connect to a service exposed by an APIRule
  • Connection refused errors occur when you want to use your custom domain
  • You receive the could not resolve host error when you want to use your custom domain
  • A resource is ignored by the controller
  • The Issuer Custom Resource fails to be created
  • The Kyma Gateway is not reachable
  • The Pods are stuck in Pending/Failed/Unknown state after an upgrade
  • There are Issues when creating an APIRule - Various reasons

• Learn something more about:

  • Authorization configuration
  • Allowed domains in API Gateway Controller
  • Blocked services in API Gateway Controller

• Analyze configuration details for:

  • The ORY chart