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

Plugin schema not found on Control Plane #12639

Closed
1 task done
lays147 opened this issue Feb 26, 2024 · 1 comment
Closed
1 task done

Plugin schema not found on Control Plane #12639

lays147 opened this issue Feb 26, 2024 · 1 comment

Comments

@lays147
Copy link

lays147 commented Feb 26, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

3.5.0

Current Behavior

Hi, I'm using Kong on Hybrid mode, and while I use decK to configure some custom plugins, the schema of them is not found on the Control Plane.

Error: building state: add defaults to plugin 'jwt-validator-plugin': retrieve schema for jwt-validator-plugin from Kong: HTTP status 404 (message: "No plugin named 'jwt-validator-plugin'")

I can see on the Data Plane logs that my plugins start and are loaded. But nothing about them is registered to the Control Plane.
Checking the logs of the control plane on "debug" mode, also does not show the plugins being loaded.

Running the container locally, as one, this problem does not happen and the plugins are registered correctly. And it uses the same kong.conf that I have for production environment for both DP and CP.

I don't know whether this is a bug or more of a question, but since google does not help me, and this feels like a bug, I'm posting in it here.

Upon checking Kong Config, I can see that my plugins are declared:
image
image

And this also happens for the ddtrace plugin installed via luarocks, not only with my custom plugins.

Expected Behavior

The plugins loads correctly on the Control Plane and decK can configure it.

Steps To Reproduce

No response

Anything else?

No response

@lays147
Copy link
Author

lays147 commented Feb 26, 2024

Never mind. Apparently, an environment variable kong_plugins was set up with bundled value that overwritten what the kong.conf configure it.

@lays147 lays147 closed this as completed Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant