Skip to content

Let the ClusterFilter API to use a ConfigMap reference with namespace #1470

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tobschli opened this issue Feb 13, 2025 · 0 comments
Open
Labels
namespace assumption issue complaining about the namespace assumptions

Comments

@tobschli
Copy link

Is your feature request related to a problem? Please describe.

I am facing a problem where another Kubernetes API is interacting with the ClusterFilter API, specifically the ConfigMap reference of the Lua script that one can configure (ClusterFilter.spec.filters[].Lua.Script).

This is of type ConfigMapKeySelector, which in turn has a LocalObjectReference inside it.
According to documentation of this type:

LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.

The problem herein lies that the ClusterFilter API is a non-namespaced resource.
Therefore, other APIs do not know that the referenced ConfigMap is meant to be in the namespace of fluent-bit.

Describe the solution you'd like

It would be nice to not have any implicit namespace assumption, but use something like ObjectReference instead, enabling other APIs to also know where this ConfigMap lives.

Additional context

No response

@cw-Guo cw-Guo added the namespace assumption issue complaining about the namespace assumptions label Mar 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
namespace assumption issue complaining about the namespace assumptions
Projects
None yet
Development

No branches or pull requests

2 participants