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

Allow configuring additional plugins for Dataplane - Kong Gateway #380

Closed
3 tasks
Tracked by #371
programmer04 opened this issue Jun 27, 2024 · 0 comments · Fixed by #476
Closed
3 tasks
Tracked by #371

Allow configuring additional plugins for Dataplane - Kong Gateway #380

programmer04 opened this issue Jun 27, 2024 · 0 comments · Fixed by #476
Assignees
Labels
area/feature New feature or request release/required
Milestone

Comments

@programmer04
Copy link
Member

Problem Statement

The relationship between an instance of CRD introduced in

and instance of Dataplane needs to be established. Extend with an additional field that matches the name of CRD, eg.

  • GatewayConfiguration -> spec.dataPlaneOptions.pluginsToInstall
  • DataPlane -> spec.pluginsToInstall

src

Kubernetes ConfigMap has to be mounted as a file in the proper paths of Kong Gateway, also environment variables have to be properly configured to make Kong Plugin available for Kong Gateway to use and be configured with KIC's CRD KongPlugin.

diagram

What is in the blue box is in the scope of this issue.

In scope are only LUA plugins without additional dependencies. To add them put plugins in a dedicated directory accessible by Kong Gateway and provide it via environment variable KONG_LUA_PACKAGE_PATH (it allows configuration like e.g. "/opt/?.lua;;"). All plugins must be in that directory.
The name of the plugin needs to be added to the variable KONG_PLUGINS (e.g. KONG_PLUGINS=”bundled,myplugin” where ”bundled” enables Kong default, built-in plugins.

References: Gateway docs, KIC docs

Acceptance Criteria

  • Plugin can be configured and used
  • statuses about attachment are in place
  • referenced plugins can't be removed by mistake
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 release/required
Projects
None yet
1 participant