Cluster ‘xxx’ Not Found Error When Adding Fluentd Access Log to Listener

Hi everyone,

I’m encountering an issue when trying to add a Fluentd access log to a listener in Envoy. I receive the following error:

[2024-10-09 18:05:42.405][75338004][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:138] gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) testlstnrnaJDny: cluster 'abc' was not found

However, the Fluentd cluster abc is clearly added, as shown below:

{
    "dynamic_active_clusters":
    [
        {
            "cluster":
            {
                "@type": "type.googleapis.com/envoy.config.cluster.v3.Cluster",
                "alt_stat_name": "aasdaa",
                "load_assignment":
                {
                    "cluster_name": "abc",
                    "endpoints":
                    [
                        {
                            "lb_endpoints":
                            [
                                {
                                    "endpoint":
                                    {
                                        "address":
                                        {
                                            "socket_address":
                                            {
                                                "address": "1.1.1.1",
                                                "port_value": 80
                                            }
                                        }
                                    }
                                }
                            ]
                        }
                    ]
                },
                "name": "abc",
                "type": "STATIC"
            },
            "last_updated": "2024-10-09T15:05:42.392Z",
            "version_info": "12a56d24a2dca4e5778852ecdf1aa919a78e9ca35f729bdb9a7c71998cc288dc"
        }
    ]
}

Despite the cluster being active and correctly configured, Envoy fails to recognize it when applying the listener configuration.

Any insights or suggestions on what might be causing this discrepancy would be greatly appreciated. Thanks in advance for your help!

Note: When I assign the same cluster abc to a route, it works without any issues.