Skip to content

fix(tenant-2): add protocol to cross_node_links for ELASTICSEARCH_HOSTS - #13

Merged
artemnikitin merged 1 commit into
mainfrom
fix/tenant-2-kibana-protocol
Jun 28, 2026
Merged

fix(tenant-2): add protocol to cross_node_links for ELASTICSEARCH_HOSTS#13
artemnikitin merged 1 commit into
mainfrom
fix/tenant-2-kibana-protocol

Conversation

@artemnikitin

@artemnikitin artemnikitin commented Jun 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add protocol: "http" to cross_node_links in tenant-2/kibana.yaml

Why

Follow-up to #12. cross_node_links without protocol injects a bare host:port string (10.30.0.3:9200). Kibana's config validation requires a full URI with scheme and rejects it:

[FATAL][root] Reason: [config validation of [elasticsearch].hosts]:
- [config validation of [elasticsearch].hosts.0]: expected URI with scheme [http|https].

Adding protocol: "http" causes the controller to inject http://10.30.0.3:9200, matching what the same-node links mechanism already does (http://172.16.0.2:9200).

🤖 Generated with Claude Code

Kibana requires a full URI (http://host:port) for elasticsearch.hosts.
cross_node_links without protocol injects bare host:port, which fails
Kibana config validation: "expected URI with scheme [http|https]".

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@artemnikitin
artemnikitin merged commit 7f0a4ab into main Jun 28, 2026
3 checks passed
@artemnikitin
artemnikitin deleted the fix/tenant-2-kibana-protocol branch June 28, 2026 13:50
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.

1 participant