mirror of
https://github.com/holos-run/holos.git
synced 2026-03-22 02:05:00 +00:00
f83781480f
Problem: The default gateway in one cluster gets server entries for all hosts in the problem. This makes the list unnecessarily large with entries for clusters that should not be handled on the current cluster. For example, the k2 cluster has gateway entries to route hosts for k1, k3, k4, k5, etc... Solution: Add a field to the CertInfo definition representing which clusters the host is valid on. Result: Hosts which are valid on all clusters, e.g. login.ois.run, have all project clusters added to the clusters field of the CertInfo. Hosts which are valid on a single cluster have the coresponding single entry added. When building resources, holos components should check if `#ClusterName` is a valid field of the CertInfo.clusters field. If so, the host is valid for the current cluster. If not, the host should be omitted from the current cluster.