-
Notifications
You must be signed in to change notification settings - Fork 404
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
[Discussion]discussion on archiving yurt-app-manager, raven-controller-manager, yurt-app-manager-api #1414
Comments
Yes, we should archive these repositories and note in the Readme that we have migrated these components to yurt-manager component in openyurtio/openyurt repo. |
LGTM, archiving repo also reduce our work, such as maintaining doc of previous version, links in which will become invalid if we make these repo private. |
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. |
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. |
All these three repos: yurt-app-manager, raven-controller-manager, yurt-app-manager-api have been archived, so i will close this issue. |
What would you like to be added:
As you known, we have migrated controllers, webhooks, and apis from these repos(yurt-app-manager, raven-controller-manager, yurt-app-manager-api ) to yurt-manager component in openyurtio/openyurt repo.
see the detail information for context.
At present, controllers and webhooks migration almost have been completed, so it is convenient to manage OpenYurt by archiving these repos.
Why is this needed:
stop pull requests and issue discussion for these repos because these repos will not be maintained.
others
/kind feature
The text was updated successfully, but these errors were encountered: