IP white list in Kong using IP restriction plugin ingress-based about kong

[brentos]

KongClusterPlugin can be used in two ways:

1. With the label global: "true", in which case it will be applied globally for all ingresses.
2. Without the label global: "true", in which case you must annotate your ingresses to have the plugin applied.

Additionally, KongPlugin is a namespaced resource, so they can only be applied to ingresses in the same namespace. KongClusterPlugin is not namespaced and can be used by any ingress in any namespace.

I hope that clears things up, let me know if you still have more questions.

[ADD-SP]

@randmonkey Could you please take a look? I'm not familiar with KIC.

[brentos]

You've set the label global: "true" which will make the plugin a global plugin instead of scoped to route, service, etc. Remove the global: "true" label and it should work how you want.

[juranir]

@brentos I understand your comment, but if I have the same configuration (the same set of ips) and I want to add this plugin to several ingress/services in different namespaces, do I have to duplicate the plugin code for each namespace? I thought a global plugin was just a plugin available to all NS, but I still need to add it to the component(ingress, service, etc) I want to use.

[juranir]

Thank you very much @brentos, I was confused about the concept of KongClusterPlugin and the global flag. Now it's very clear