Skip to content
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

[feature request] use sealer to install OpenYurt cluster #656

Closed
rambohe-ch opened this issue Dec 6, 2021 · 4 comments
Closed

[feature request] use sealer to install OpenYurt cluster #656

rambohe-ch opened this issue Dec 6, 2021 · 4 comments
Labels
kind/feature kind/feature kind/good-first-issue kind/good-first-issue wontfix

Comments

@rambohe-ch
Copy link
Member

rambohe-ch commented Dec 6, 2021

What would you like to be added:
In order to improve the experience of using OpenYurt, how about to use sealer(https://github.com/alibaba/sealer) to install OpenYurt cluster? and then we can use sealer to replace yurtctl init.

Why is this needed:
End user can easily experience OpenYurt in different environments.

others
/kind feature

@rambohe-ch rambohe-ch added kind/good-first-issue kind/good-first-issue kind/feature kind/feature labels Dec 6, 2021
@cuisongliu
Copy link
Contributor

need write Kubefile + plugin customize openyurt cluster

1 Kubefile add app-manager ,tunnel-agent,tunnel-server
2. plugin before install add yurthub static pod
3. plugins after install replace kubelet conf

@Peeknut
Copy link
Member

Peeknut commented Dec 10, 2021

Maybe we can keep yurtctl init and refactor yurtctl init to call sealer, which is more user-friendly as users only need to learn how to use yurtctl rather than sealer.

And how about creating an issue about this (refactor yurtctl init)?

@rambohe-ch
Copy link
Member Author

Maybe we can keep yurtctl init and refactor yurtctl init to call sealer, which is more user-friendly as users only need to learn how to use yurtctl rather than sealer.

And how about creating an issue about this (refactor yurtctl init)?

@Peeknut agree +1

@stale
Copy link

stale bot commented Mar 10, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 10, 2022
@stale stale bot closed this as completed Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature kind/feature kind/good-first-issue kind/good-first-issue wontfix
Projects
None yet
Development

No branches or pull requests

3 participants