After 5 years of foot-dragging they finally close the ticket to community protest:
This feature request is being closed as our current focus isn’t in this area.
We appreciate your input and contribution to improving our product. While this feature may have merit, we need to prioritize our efforts elsewhere at this time.
If you’d like to provide additional context about why this feature is important, please feel free to leave a comment on this issue. This will help us better evaluate the feature if we revisit this area in the future.
Thank you for your understanding and continued support in helping us build a better product.
Company A permits federation of project 2 with contractor B who agrees. Oh look! No need to add 21 people to your AD. Contract done? De-fed.
Google feds with GH for AOSP dev, because it’s 2023. Users don’t need to even know where the repo is hosted or whether the real meat is another hop inside.
Company “BCFerries”, an imaginary organization, happens to run the largest fleet of mobile DCs in the country, with each mobile DC being 6 HA racks, three on a side, dehumidifiers o-plenty. Engineers stationed aboard need to lob tickets and hot fixes on the go, and sub them for review when the mobile DCs get a good link, 30 min out of every 2 hours. Roaming 2/2/2tb node swaps spit with the stationary nodes when it smells the VPN, and then gets ready to go again.
Repeat that above, but say ‘Maersk’. I’m betting evergreen/evergiven is on VSS.
Enough examples?
Running a federated GL is conceivably a set-it-and-forget-it like a lot of federated stuff already is, and you debug the glitches and patch like normal.
Given the 5GLs I still run were all installed by VMware/terraform/chef/RPM, patched automatically with package promotion and watched for anomalies, it’s already negligible effort. Double nothing is …let’s see …carry the 0 …integrate the square …nothing.
I don’t understand anything you just said.