配置redis出问题

[fzlinjianhui]

部署环境：docker all-in-ont 2.2.2.rc.2

1. 创建一个服务来源：

2.在我自己编写的插件中（这个插件我原来验证过是正常的，redis也是跟我原来用的是一样的）使用这个redis，我插件的配置文件：

观察到插件加载的时候报错日志：
[2026-05-12 04:21:16.870][282][error][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1519] wasm log: [ai-billing-pusher] [nil] reliable push redis config invalid: cluster_name= service_name= service_port=6379 database=0 timeout_ms=1000 key_prefix=ai-billing-pusher:reliable username_set=false password_set=false

这是billing-receiver 的配置：

[rafshanDev90]

🛠️ Analysis & Root Cause

The error log shows that the Redis configuration validation failed because both the cluster_name and service_name properties evaluated to completely empty strings:

...redis config invalid: cluster_name= service_name= service_port=6379 ...

When deploying a custom Wasm plugin that interfaces with Redis, Envoy requires a valid target routing definition. Without an explicit Envoy cluster name or gateway service name, the plugin cannot initiate a socket connection.

💡 How to Fix

Update your custom plugin configuration YAML to explicitly define either the cluster_name or service_name mapped to your Redis instance.

Inside your custom plugin configuration layout:redis:

service_name: "redis.static" # 👈 Replace with your actual service or K8s name
service_port: 6379
database: 0
timeout_ms: 1000
key_prefix: "ai-billing-pusher:reliable"

ℹ️ Note: If your environment bypasses service definitions and uses direct Envoy clusters instead, replace service_name with cluster_name: "your_redis_cluster".

---

✅ Checklist

• Verify Key Casing: Ensure your keys match the exact naming convention expected by your Wasm deserializer (e.g., snake_case vs camelCase).
• Cross-Check Upstreams: Match this configuration directly with the upstream targets specified in your billing-receiver configuration profile.