This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Design login command #30
Labels
area/cli
area/iam
Related to identity access management
kind/design
Issue/PR as related to design.
lifecycle/active
migration/imported
not-core-cli
priority/important-soon
Milestone
Review the design of the login plugin
Collated Context
Context from 2021-01-29 17:51:04
User: timothysc
At minimum we should have a plan in place.
Context from 2021-02-17 15:28:45
User: mattmoyer
Some issues to consider in this design:
How do we bootstrap trust into a management cluster where I don't have the self-signed CA bundle yet? This is very similar to the boostrapping problem in
kubeadm join
, and I think we could use a similar approach to kubeadmHow do we express "login to SaaS" and "login to TKG" in the least confusing way? Can we unify the "login to SaaS" flow across multiple CSP-based services (TMC + TSM)?
I'm sure there are a bunch more things to consider, this is just some rough notes after discussions yesterday.
The text was updated successfully, but these errors were encountered: