I get what you are saying. IMHO this is one of those cases where Docker’s development-side roots come through, even when trying to do something operations.
Authenticating against GitHub is fine in one of two cases:
- You are doing something development - after all, GH is part of your dev cycle
- You are in an extremely small team
The moment those are not true - you have multiple teams with separate responsibilities, e.g. development and ops, let alone you are working in the operational space - relying on GitHub to manage your internal production operations, not development or new deployments, makes many people very nervous and completely breaks their actual flows and processes.
How would I tell an ops team of 5 people to go set up github (or bitbucket or …) accounts so they can manage their operational environment? They would laugh me out of the room. The developers? They would love it. But the ops? Never.
So, yeah, LDAP works for a team that has enterprise infrastructure and authentication, but that makes the initial setup and integration curve much higher. I am setting up a basic structure for a team, let them choose among multiple orchestrators… and I have no easy way to just get them going. I am not going to get them github accounts (for production use or for testing), nor would they agree, and setting up an LDAP server just for this is kind of crazy.