-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify manual resource joining process #10340
Comments
@xinding33 Now that Cloud supports Joining Nodes and Proxies in AWS, what do you guys think about supporting three join modes, |
To make the PRs smaller, I'm doing each kind of resource individually,
|
@xinding33 we don't have currently an Should we implement one (maybe following this suggestion) or leave kubernetes out of this issue for now? |
@mcbattirola Yes, let's add it. Please propose a design and @xinding33 will review. |
an update about Kubernetes: I talked with @rishibarbhaya-design, I'll define what steps we will have in the wizard and validate it, then Rishi will provide a design. |
Closing this issue since the remaining work is now being tracked in #11465. |
What
Is there any reason we have steps 2 and 3 in the manual resource joining process instead of embedding an already-issued join token in step 4?
If we can simplify this process, we'd make it easier for users to add their first resource.
How
Generate a join token when automatically in step 4 and delete steps 2 and 3.
Why
Easier to add resource --> reduce time to first value.
The text was updated successfully, but these errors were encountered: