[Feature]: Native cluster-cluster communication for federated solutions between trusted parties

[casperlundberg]

Area

Other

User problem

I have multiple sites, each having their own cluster, but I want to share their capabilities from a single endpoint so I can use all clusters together when I want more than what my main cluster can provide.

Desired outcome

Seamless cluster-cluster communcation where any cluster can be reached if wanted, and each cluster acts as a normal cluster but it can also reach and use other resources outside of itself via the federation. One use case is that if the local cluster in use doesn't have the capabilities to handle a request, it migrates to another of my clusters with capabilities to handle the request.

Alternatives considered

No response

Compatibility and security implications

No response

Validation approach

No response

Confirmations

• I searched existing issues for duplicates.
• I agree to follow the Code of Conduct.

[CryptoJones]

Cross-linking PR #38 as a possible building block, not a complete federation implementation.

#38 does not add native cluster-to-cluster federation, shared membership, remote discovery, cross-cluster scheduling, or policy negotiation. It does, however, give one cluster a supported authenticated OpenAI-compatible ingress that another trusted system could call.

So for a first federation adapter or higher-level router, #38 supplies the “one cluster can expose a keyed endpoint to another trusted caller” piece. The larger #53 design would still need to decide how clusters advertise capabilities, choose remote clusters, handle trust, and surface routing/failover behavior.