-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update standalone agent manifest conditions and scheduler and controllermanager default hosts #28675
Update standalone agent manifest conditions and scheduler and controllermanager default hosts #28675
Conversation
…lermanager default hosts
This pull request does not have a backport label. Could you fix it @MichaelKatsoulis? 🙏
NOTE: |
Pinging @elastic/integrations (Team:Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just add a changelog entry and should be ready to merge.
This pull request is now in conflicts. Could you fix it? 🙏
|
…e-agent-manifest-conditions
What does this PR do?
After #27691
kubernetes.pod.labels
are being populated underkubernetes.labels
. The standalone agent manifest conditions have to be updated.As part of this PR also the default hosts for
controllermanager
andscheduler
are updated with the secure ports.Why is it important?
Without this PR the conditions in the kubernetes autodiscover provider don't match any pod so the scheduler and controllermanager data streams do not work.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.