Do not set Kibana server.name

[naemono]

re: #8929

From my local testing, this defaults properly to the pod name, which makes stack monitoring a bit more useful in the case of multiple Kibana instances.

[prodsecmachine]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Copilot]

Pull request overview

This PR removes the automatic setting of the server.name configuration in Kibana deployments to allow Kibana to default to using the pod name instead. This improves the usefulness of stack monitoring when multiple Kibana instances are deployed, as each instance will have a unique identifier based on its pod name rather than all sharing the same Kibana resource name.

Key Changes

• Removed automatic setting of server.name in the base Kibana configuration
• Updated test expectations to reflect the absence of server.name in generated configurations

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
pkg/controller/kibana/config_settings.go	Removed the ServerName: kb.Name entry from the base settings map, allowing Kibana to use its default server name (pod name)
pkg/controller/kibana/config_settings_test.go	Updated test fixtures defaultConfig and defaultConfig8 to remove the expected name: "testkb" line from server configuration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[pebrc]

Change looks good to me code wise. But I am trying to assess any issues this might cause for existing users.

Monitoring History Continuity:
If you're using Stack Monitoring:
Historical monitoring data will show the old name
New monitoring data will show the new name
This might make it look like you have two different Kibana instances in your monitoring dashboards
Queries or dashboards filtering by instance name will need to be updated.

kbn-name header:
Its value is taken from the server.name setting. Any external integration or script that relies on that header value might break. I am not sure it is a legitimate expectation. Also any custom query that relies on kibana_stats.kibana.name could potentially break.

[pebrc]

LGTM
Let's make sure to include this in the breaking changes documentation for the next release where we

• explain our motivation (official Kibana documentation)
• mention the workaround for uses that want to restore the original (incorrect) behaviour.