We’ve upgraded the Kong to 2.0.4 and we noticed if there was any malformed or bad configuration in plugins then the whole functionality of Kong would go down whereas in Kong 1.4.1, it has worked perfectly and bad or malformed configuration would be ignored by Kong.
How could we solve this problem, it’s about the validation of plugin’s configuration ?
Are you using Kong in Kubernetes as an Ingress Controller?
Yes, We have been using Kong in Kubernetes as an Ingress Controller. It’s really wonderful because in 1.4.1 we haven’t had that validation issue
Moreover, Due to Openshift 3.x doesn’t support “admission controller” in production level, we’re not able to use this feature to solve our problem.