Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple plugins of same type on Ingress and Service #272

Closed
hbagdi opened this issue Apr 15, 2019 · 2 comments
Closed

Support multiple plugins of same type on Ingress and Service #272

hbagdi opened this issue Apr 15, 2019 · 2 comments
Labels
area/feature New feature or request

Comments

@hbagdi
Copy link
Member

hbagdi commented Apr 15, 2019

Problem

Currently, a KongPlugin of one type can be added once to an Ingress/Service. There are use-cases when multiple such plugins, for a combination of a Route and Consumer need to be instantiated.

Solution

Add support for multiple plugins of the same type in plugins.konghq.com annotation.
#250 will also solve problems for cases when a plugin needs to be instantiated at a consumer level and not for a combination of a Consumer and Service.

The solution requires Kong/deck#13 to be implemented first, which can then be leveraged by the Ingress Controller to make this possible for database-backed deployments.

@hbagdi
Copy link
Member Author

hbagdi commented Jul 2, 2019

An update:

Kong Ingress Controller 0.5.0 brings in support for configuring Consumer-level plugins in Kong which solves part of this problem.

There could be use-cases which require Kong to be configured with a plugin for a specific consumer and route or a consumer and a service and this is not possible as of today.

@hbagdi hbagdi added the area/feature New feature or request label Aug 12, 2019
@hbagdi
Copy link
Member Author

hbagdi commented Jan 7, 2020

This is now possible with 0.7.0 version.

@hbagdi hbagdi closed this as completed Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant