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:
|
ChrsMark
left a comment
There was a problem hiding this comment.
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.labelsare being populated underkubernetes.labels. The standalone agent manifest conditions have to be updated.As part of this PR also the default hosts for
controllermanagerandschedulerare 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.asciidocorCHANGELOG-developer.next.asciidoc.