Open tnthornton opened 3 months ago
I love the idea that you're thinking this through!!! ❤️ I agree that this is one of the more confusing bits of the up CLI.
I'm not an expert with the Kubeconfig schema, so a couple of questions that may be stupid:
up login
stores the session ID in the configuration file. Is there a place for that in the kubeconfig? Would it a token in the AuthInfo? (I'm not really pushing for a technical decision, just making sure it's feasible.)
@AlainRoy all good questions. I think we have a number of options with how we could address those concerns/questions. If we get buy in that this is reasonable enough to move to do a one pager/POC, we can explore possible answers to each of those.
What problem are you facing?
As usage has grown for
up
, we've gone through a few different phases of attempts to manage authentication/contexts with different systems:This has left us in a state where:
How could Upbound help solve your problem?
This issue proposes that we replace the config and profile constructs with kubeconfig semantics:
Within the kubeconfig, we could:
In general this will benefit current consumers and future consumers: