fix(tenant-2): use host_port in cross_node_links - #12
Merged
Conversation
The scheduler placed tenant-2-kibana and tenant-2-elasticsearch on different nodes. `links` only resolves same-node guest IPs, so ELASTICSEARCH_HOSTS was never set and Kibana panicked at boot. Switch to `cross_node_links` so the controller injects the peer node's host_ip:host_port at reconcile time. Add port_forwards on elasticsearch to expose 9200 on the host so the controller has a host_port to resolve. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The enricher maps `host_port` → CrossNodeLinks.HostPort. Using `port` left HostPort=0, so the controller injected ELASTICSEARCH_HOSTS as 10.30.0.3:0 instead of 10.30.0.3:9200. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
artemnikitin
added a commit
that referenced
this pull request
Jun 28, 2026
…TS (#13) ## 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](https://claude.com/claude-code) Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cross_node_linksfield:port→host_portintenant-2/kibana.yamlWhy
Follow-up to #11. The enricher maps
host_port→CrossNodeLinks.HostPort. Usingport: 9200leftHostPort: 0in the desired state, so the controller resolvedELASTICSEARCH_HOSTSto10.30.0.3:0instead of10.30.0.3:9200.🤖 Generated with Claude Code