8000 Certificate error occurred while collecting kubernetes_events logs in Fluent Bit. · Issue #9922 · fluent/fluent-bit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Certificate error occurred while collecting kubernetes_events logs in Fluent Bit. #9922

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.

Sign up for GitHub

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

Jump to bottom
Closed
pandihao opened this issue Feb 6, 2025 · 2 comments
Closed

Certificate error occurred while collecting kubernetes_events logs in Fluent Bit. #9922

pandihao opened this issue Feb 6, 2025 · 2 comments
Labels
Stale status: waiting-for-triage

Comments

@pandihao
Copy link
pandihao commented Feb 6, 2025 •
edited
Loading

Bug Report

Describe the bug

Certificate error occurred while collecting kubernetes_events logs in Fluent Bit.

To Reproduce

  1. Error log is as follows:

[2025/01/03 09:21:33] [error] [input:kubernetes_events:kubernetes_events.1] upstream connection initialization error
[2025/01/03 09:21:33] [error] [tls] certificate verification failed, reason: self-signed certificate (X509 code: 18)
  • Steps to reproduce the problem:

Expected behavior

  1. Fluent Bit is installed using Helm, and the content of the values.yaml file is as follows.

  inputs: |

    [INPUT]
        Name            kubernetes_events
        Tag             k8s_event
        kube_url        https://kubernetes.default.svc

Your Environment


kubernetes version:  Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.14", 
Linux version: centos7.9
fluent-bit appVersion ：3.2.2
@github-actions GitHub Actions
Copy link
Contributor
github-actions bot commented May 8, 2025

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label May 8, 2025
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale status: waiting-for-triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pandihao
0