Skip to content

Conversation

poblahblahblah
Copy link
Contributor

@poblahblahblah poblahblahblah commented Jun 3, 2025

This allows the consumer to set hostNetwork for the otellogs daemonset. This defaults to false to preserve the current behavior.

For some background on this we run a handful of large clusters where IP space is at a premium. In our larger clusters this would save ~2000 IPs, which would be great to claw back!

Checklist

  • Changelog updated or skip changelog label added
  • Documentation updated
  • Template tests added for new features
  • Integration tests added or modified for major features

@poblahblahblah poblahblahblah requested a review from a team as a code owner June 3, 2025 13:00
@poblahblahblah poblahblahblah changed the title otellogs.daemonset: allow for hostNetwork feat: allow for hostNetwork in otellogs.daemonset Jun 3, 2025
@echlebek
Copy link
Contributor

Hi @poblahblahblah, just wondering if you have successfully tried this on your (EKS?) cluster. It seems to me that you would also need dnsPolicy: ClusterFirstWithHostNet?

We require new integration tests that exercise this feature before we can consider it for merge. Can you please add them?

Regarding the CI failure for the changelog, I think it's because you used "feat" instead of "added", which we have specified in the towncrier configuration.

Regarding the CI failure for the operator instrumentation, there could be a flaky test here. We will look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants