Plugin Compatibility

–

–

–

–

–

–

In DB-less, hybrid mode, and Konnect, the cluster config strategy is not supported. Use redis instead. In Serverless gateways only the local config strategy is supported.

–

–

–

Application registration is available in Konnect, but doesn’t require this plugin.
Learn how to Enable Application Registration in Konnect.

–

–

–

–

–

–

The time-to-live (ttl) does not work in Konnect or hybrid mode. This setting determines the length of time a credential remains valid.

This plugin is not available in Konnect, and has limitations in hybrid mode:

• Konnect automatically encrypts key authentication credentials at rest, so encryption via this plugin is not necessary. Use the regular Key Auth plugin instead.
• The time-to-live (ttl) does not work in hybrid mode. This setting determines the length of time a credential remains valid.

–

–

Serverless Gateways: This plugin is not supported in serverless gateways because the TLS handshake does not occur at the Kong layer in this setup.

This plugin can’t be used in Konnect, hybrid, or DB-less modes. It needs to generate and delete tokens, and commit those changes to a database on the same node.

–

In Serverless gateways only the cookie config session storage is supported.

In Serverless gateways only the cookie config session storage is supported.

–

In Serverless gateways only the memory cache strategy is supported.

–

Serverless Gateways: This plugin is not supported in serverless gateways because the TLS handshake does not occur at the Kong layer in this setup.

–

–

–

–

–

Serverless Gateways: This plugin is not supported in serverless gateways because the TLS handshake does not occur at the Kong layer in this setup.

Serverless Gateways: This plugin is not supported in serverless gateways because the TLS handshake does not occur at the Kong layer in this setup.

–

The Canary plugin is not designed for a Kubernetes-native framework, and shouldn’t be used with the Kong Ingress Controller. Instead, use the Gateway API to manage canary deploys.

–

This plugin’s API doesn’t work in hybrid mode, as it targets data that only exists on data planes, and data planes can’t use Kong’s Admin API. In Serverless gateways only the memory config strategy is supported.

In DB-less, hybrid mode, and Konnect, the cluster config strategy is not supported. Use redis instead.

–

–

–

In Serverless gateways only the memory config strategy is supported.

In Konnect, DB-less, and hybrid modes, the cluster config policy is not supported.

For DB-less mode, use one of redis or local; for Konnect and hybrid mode, use redis, or local for data planes only. In Serverless gateways only the local config policy is supported.

In Konnect, DB-less, and hybrid modes, the cluster config strategy is not supported.

For DB-less mode, use one of redis or local; for Konnect and hybrid mode, use redis, or local for data planes only. In Serverless gateways only the local config strategy is supported.

–

–

–

In Konnect, DB-less, and hybrid modes, the cluster config policy is not supported.

For DB-less mode, use one of redis or local; for Konnect and hybrid mode, use redis, or local for data planes only. In Serverless gateways only the local config policy is supported.

–

–

–

–

–

Dedicated Cloud Gateways: If you use the IAM assumeRole functionality with this plugin, it must be configured differently than for hybrid deployments in Konnect.

–

Not bundled with Kong Gateway.

Installed as a LuaRocks package.

Dedicated Cloud Gateways: This plugin is not supported in Dedicated or Serverless Cloud Gateways because it depends on a local agent, and there are no local nodes in Dedicated or Serverless Cloud Gateways.

–

–

Dedicated and Serverless Cloud Gateways: This plugin is not supported in Dedicated or Serverless Cloud Gateways because it depends on the Admin API and the Status API, which aren’t accessible in that setup.

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

Dedicated Cloud Gateways: This plugin is not supported in Dedicated or Serverless Cloud Gateways because it depends on a local agent, and there are no local nodes in Dedicated or Serverless Cloud Gateways.

–

–

–

Dedicated and Serverless Cloud Gateways: This plugin is not supported in Dedicated or Serverless Cloud Gateways because it depends on a local agent, and there are no local nodes in Dedicated or Serverless Cloud Gateways.

–

–