Upgrade from Kong 3.8.0 to 3.9.0 rate-limiting plugin depreciation warning

[ego93]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.9.0

Current Behavior

When I upgraded from Kong 3.8.0 to 3.9.0 I got millions of log warning messages about the rate-limiting plugin having deprecated config.redis*

Example: 1407#0: *50235 [kong] init.lua:904 rate-limiting: config.redis_ssl is deprecated

Expected Behavior

When I upgrade I expect config that has moved location to be auto-updated

Steps To Reproduce

1. Kubernetes 1.31.x
2. Running Kong 3.8.0 in DB-less mode deployed with Helm using chart version 2.46.0
3. Have an ingress using rate-limiting plugin on the route
4. Upgrade chart to 2.48.0 making sure image is 3.9.0
5. See warning

Anything else?

Kong is in DB-Less mode
Warning comes from kong_admin service
The plugins and ingress routes are deploy in additional helm charts in different namespaces to kong

[Water-Melon]

This field will be automatically replaced with redis.ssl in version 3.x. If you are using DB-less mode, you can modify the Admin API request parameters when applying the configuration, changing redis_ssl to redis.ssl.

[ego93]

@Water-Melon I'm not using any redis in my config nor has it ever been configured yet I still get the depreciation warning

[ego93]

More info here is the full deployed config of the rate-limit plugin that was deployed with Kong 3.8.0

  "config": {
    "redis_host": null,
    "policy": "local",
    "fault_tolerant": true,
    "hide_client_headers": false,
    "minute": null,
    "redis_timeout": 2000,
    "redis_server_name": null,
    "redis_ssl_verify": false,
    "redis": {
      "timeout": 2000,
      "password": null,
      "server_name": null,
      "host": null,
      "ssl": false,
      "username": null,
      "port": 6379,
      "database": 0,
      "ssl_verify": false
    },
    "error_code": 429,
    "error_message": "API rate limit exceeded",
    "sync_rate": -1,
    "redis_ssl": false,
    "redis_password": null,
    "redis_port": 6379,
    "redis_username": null,
    "second": 10,
    "header_name": null,
    "hour": null,
    "day": null,
    "month": null,
    "year": null,
    "path": "/",
    "limit_by": "ip",
    "redis_database": 0
  },

Here is the config I'm defining in helm

    config:
      path: /
      second: 10
      limit_by: ip
      hide_client_headers: false

My understanding is that the redis_* config is being deployed with default values. I understand this is done for compatibility before the 4.0 release, but the over-logging of deprecation warnings in the Kong proxy logs is too much.

[github-actions]

This issue is marked as stale because it has been open for 14 days with no activity.

[ego93]

@Water-Melon any further comment on this?

[mcen1]

I'm also encountering this issue. Like the OP, I am not using redis anywhere and my policy is "local" for the rate-limiting, so I don't understand why this error is appearing.

edit: I switched to kong/kong-gateway:3.10.0.2-rhel and these errors do not appear so it seems specific to the ubuntu container to me.