Dbless K4K8s ( version 2.0 ) transformer plugins are not working as expected

Questions
#1

hi
I am trying to use below 2 plugin with K4K8S (2.0.4) dbless deployment
exit-transformer and response-transformer-advanced
As per this document both the plugins are enabled for this release but

exit-transformer straight away giveing me not enabled error
“name”: “plugin ‘exit-transformer’ not enabled; add it to the ‘plugins’ configuration property”

whereas response-transformer-advanced works only the json that has changes in layer 1 and not the nested json i.e

{
“errors”: [
{
“code”: “400”,
“title”: “No Sufficient Rights”,
“detail”: “You don’t have sufficient scopesto access the data”,
“meta”: {}
}
]
}

to

{
{
“code”: “400”,
“title”: “Changed”,
“detail”: “changed”,
“meta”: {}
}
}

but could not changed it to

{
“errors”: [
{
“code”: “400”,
“title”: “changed”,
“detail”: “changed”,
“meta”: {}
}
]
}

Could you confirm if these are known limitation with both the plugins or if there is an workaround available

  - name: response-transformer-advanced
    service: transactions-srv
    enabled: true
    config:
      replace:
        json: [new-param:some_value]
        if_status: ["400"]

reference : https://docs.konghq.com/hub/plugins/compatibility/

#2

Hi, exit-transformer and response-transformer-advanced aren’t actually available in that version. For some reasons I won’t go into here, compatibility for the kong-enterprise-k8s image is instead documented here: https://github.com/Kong/kubernetes-ingress-controller/blob/main/docs/references/plugin-compatibility.md#kong-enterprise

I recommend trying this with the kong-enterprise-edition 2.1 beta image. It does support both plugins and should work as a drop-in replacement on clusters currently using the kong-enterprise-k8s image in DB-less mode: https://docs.konghq.com/enterprise/2.1.x/kong-for-kubernetes/deployment-options/#deployment-options

I don’t have familiarity with the response-transformer-advanced issue, so for that I’ll direct you to https://support.konghq.com/support/s/

We do recommend you raise a case there first for Enterprise issues, as the support team is best-equipped to field Enterprise issues across the Enterprise product suite (e.g. here, where the issues touch on both stuff that’s specific to Kong for Kubernetes Enterprise and general plugin configuration). They’ll also be able to provide assistance if there’s any issues with your access to the kong-enterprise-edition beta images. Normally you should only need to create Docker registry credentials if you haven’t already and change the image registry and tag, as it’s separate from the kong-enterprise-k8s registry.