Skip to content

Add support for Hubble flowlogs config #12064

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
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

ErmolenkoMaxim
Copy link

@ErmolenkoMaxim ErmolenkoMaxim commented Mar 21, 2025

/kind feature

What this PR does / why we need it:
Adds support for configuring Hubble flowlogs in Cilium via Kubespray inventory.
This allows users to declaratively define flow log filtering and output settings in hubble_flowlogs_config from their inventory.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
Tested on Kubernetes 1.29 with Cilium 1.14.
Flowlogs configuration is properly mounted into the Cilium pods and validated.

Does this PR introduce a user-facing change?:

Kubespray now supports configuring advanced Hubble flow log settings for Cilium via the `hubble_flowlogs_config` inventory variable. The specified configuration is rendered as `flowlogs.yaml`, mounted into the Cilium pod, and used to customize flow log filters, output format, and export behavior.

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Mar 21, 2025
Copy link

linux-foundation-easycla bot commented Mar 21, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Mar 21, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ErmolenkoMaxim
Once this PR has been reviewed and has the lgtm label, please assign yankay for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

Welcome @ErmolenkoMaxim!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 21, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @ErmolenkoMaxim. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 21, 2025
@ErmolenkoMaxim
Copy link
Author

CLA signed.

@tico88612
Copy link
Member

@ErmolenkoMaxim It is still not signed. #12064 (comment)

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Mar 24, 2025
@ErmolenkoMaxim
Copy link
Author

@tico88612 fixed. Please proceed.

@tico88612
Copy link
Member

@ErmolenkoMaxim please fix your PR content about the release-note like this:

```release-note
```

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Mar 24, 2025
@ErmolenkoMaxim
Copy link
Author

@ErmolenkoMaxim please fix your PR content about the release-note like this:

```release-note
```

sure. please check.

@VannTen
Copy link
Contributor

VannTen commented Apr 1, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. do-not-merge/contains-merge-commits and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 1, 2025
@ErmolenkoMaxim
Copy link
Author

@VannTen retest?

@VannTen
Copy link
Contributor

VannTen commented Apr 7, 2025 via email

@ErmolenkoMaxim
Copy link
Author

@yankay @tico88612 please check

@ErmolenkoMaxim
Copy link
Author

@yankay @tico88612 kind reminder

@ErmolenkoMaxim
Copy link
Author

Check the pre-commit logs.

@VannTen could you please be more specific?

@tico88612
Copy link
Member

@ErmolenkoMaxim No promise review. Please check your pre-commit job for no errors. If there is no special reason, please fix it.

@k8s-ci-robot
Copy link
Contributor

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ErmolenkoMaxim
Copy link
Author

ErmolenkoMaxim commented Apr 23, 2025

@tico88612 pre-commit job checked and fixed. please proceed

@ErmolenkoMaxim
Copy link
Author

@tico88612 @yankay please proceed

@ErmolenkoMaxim ErmolenkoMaxim requested a review from yankay May 7, 2025 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/contains-merge-commits kind/feature Categorizes issue or PR as related to a new feature. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants