Skip to content
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

Parsers ConfigMap only has OwnerReference to first LogPipeline that gets reconciled #1879

Open
jeffreylimnardy opened this issue Feb 26, 2025 · 0 comments
Assignees
Labels
area/logs LogPipeline

Comments

@jeffreylimnardy
Copy link
Contributor

Description

When multiple LogPipelines are created, the telemetry-fluent-bit-parsers ConfigMap only has an OwnerReference to the first LogPipeline that gets reconciled.

Expected result

The telemetry-fluent-bit-parsers ConfigMap has an OwnerReference to each LogPipeline that gets created.

Actual result

The telemetry-fluent-bit-parsers ConfigMap only has an OwnerReference to the first LogPipeline which got reconciled.

Steps to reproduce

Create more than 1 LogPipeline, check the contents of the telemetry-fluent-bit-parsers ConfigMap. The OwnerReference field will only include a reference to the first LogPipline that got reconciled.

With the 2 LogPipelines created:
Image

Getting the telemetry-fluent-bit-parsers ConfigMap YAML shows only a reference to the first LogPipeline that got reconciled
Image

Troubleshooting

Release Notes


@jeffreylimnardy jeffreylimnardy added kind/bug Categorizes issue or PR as related to a bug. area/logs LogPipeline labels Feb 26, 2025
@jeffreylimnardy jeffreylimnardy self-assigned this Feb 26, 2025
@a-thaler a-thaler removed the kind/bug Categorizes issue or PR as related to a bug. label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logs LogPipeline
Projects
None yet
Development

No branches or pull requests

2 participants