I’m currently integrating a custom plugin (developed for Kong gateway) into our Kubernetes setup.
The current problem is that I have mounted the CM with the LUA files but, it don’t seem to be picked up.
For setting up this solution I followed an older custom plugins question answer from @traines but without success. I followed the following procedure
1.
kubectl create configmap custom-plugins --from-file=kong-upstream-gateway/ --namespace kong
but it doesn’t seem to work . How can validate the custom plugin is correctly available ? and where is a good description of enabling custom plugins in a kubernetes ingress controller Kong environment ?
One update since that old post: if you’re using the Helm chart, the mounts/configuration can be set up semi-automatically. That method does have some limitations at present (it doesn’t work well with plugins that have been installed into a custom image or plugins that require external libraries), but works well for simpler plugins.
Loading plugins requires several settings on top of the mounts themselves. Your mounts look fine, though you should be able to simplify the volumeMount (specifying individual files should only be necessary if your ConfigMap keys do not match the intended filenames–creating the ConfigMap from a plugin directory, as you’ve done, should set the correct names by default). For example, the generated volume sections I get from the chart look like:
After updating the YAML finally custom pluing get install but after that got next issue. Now same POD, Deployment and Replicaset throwing “CrashloopOff”. After checking the log of the pod we got following error.