fix(tenant-2): use cross_node_links for kibana→elasticsearch - #11
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>
artemnikitin
added a commit
that referenced
this pull request
Jun 28, 2026
## Summary - Fix `cross_node_links` field: `port` → `host_port` in `tenant-2/kibana.yaml` ## Why Follow-up to #11. The enricher maps `host_port` → `CrossNodeLinks.HostPort`. Using `port: 9200` left `HostPort: 0` in the desired state, so the controller resolved `ELASTICSEARCH_HOSTS` to `10.30.0.3:0` instead of `10.30.0.3: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
tenant-2/kibana.yamlfromlinkstocross_node_linksfor the Elasticsearch service discoveryport_forwards: [{host_port: 9200, vm_port: 9200}]totenant-2/elasticsearch.yamlWhy
The scheduler placed
tenant-2-kibanaandtenant-2-elasticsearchon different nodes.linksis same-node only — the agent resolves to the linked service's guest IP (172.16.0.x). Since the services were cross-node,ELASTICSEARCH_HOSTSwas never injected, causing Kibana to panic at boot with:cross_node_linksis resolved by the controller at reconcile time: it findstenant-2-elasticsearchon its node, reads thehost_portfromport_forwards, and injectsELASTICSEARCH_HOSTS=http://<host_ip>:9200into Kibana's kernel args before the service starts.🤖 Generated with Claude Code