[v18] [docs] Update Event Handler guides with Kubernetes Operator opt-in#64585
[v18] [docs] Update Event Handler guides with Kubernetes Operator opt-in#64585kshi36 wants to merge 1 commit intobranch/v18from
Conversation
…63109) * Update docs for Event Handler chart Operator opt-in * Address feedback * Edit Splunk guide with new rework * Address feedback
kshi36
added
the
no-changelog
|
Amplify deployment status
|
kshi36
changed the title
kshi36
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b757679ff
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| Change `forward.fluentd.url` to the scheme, host and port you configured for | ||
| your Logstash `http` input earlier, `https://localhost:9601`. Change | ||
| `forward.fluentd.session-url` to the same value with the root URL path: | ||
| `https://localhost:9601/`. |
There was a problem hiding this comment.
This section now supports Helm and Kubernetes Operator setups, but it still tells readers to edit only the executable keys forward.fluentd.url and forward.fluentd.session-url. In Helm-based configs those keys are fluentd.url and fluentd.sessionUrl (as shown in the shared field include), so users following the Helm path will leave the actual values unchanged and the Event Handler will keep posting to the wrong endpoint, breaking Elastic ingestion.
Useful? React with 👍 / 👎.
1 participant
Backport #63109 to branch/v18